Comment 3 for bug 2037685

I think this is what's happening: eg.search.search_lib and eg.search.pref_lib are fetched when the PreferencesComponent is initialized, but the values are null when the Search Preferences page is first loaded, and this appears to trigger an update that deletes the settings. The fetch request eventually completes and updates the page with the correct values, but this happens via applyOrgId which explicitly doesn't trigger an onChange event -- so the correct values are displayed to the user but they remain deleted behind the scenes.

I've tinkered a bit but haven't been able to come up with a fix.