When you set a search-view to default: true so that it gets used by default when a user goes to the Search page, that search-view is now used by default every single time the search_results url is hit. This means that if you have a search-view that doesn't use, say, the vanilla "term-filter", any query parameters nested under "term-filter" will be discarded and those searches will not work as expected (for example the resource-instance select widget in the resource-instance datatype). One way to fix this would be to incorporate new keys on the search-view config json to distinguish a search-view as a "globalDefault" vs one that is just the "searchViewDefault". That way a developer doesn't need to worry about side effects from their custom searchview when normal Arches search requests get sent.