I have a web map that contains features from our water network. Users of this map need to be able to perform searches on a number of layers included in the referenced map service. Specifically, they need to search Hydrants and Service Laterals by their ASSET ID field. This is a string field (no domains).
Whenever I try to add a new layer to base a search upon, the dropdown for the attributes appear to be locked to a different layer in my map. The other layers have the QUERY operations enabled so I'm not sure why it's getting hung up.
I've created a sample map to test this and I can't even access the Search Layer settings if using the same layer. I can enable the By Layer option but then it fails to bring in any drop down to add a layer. I can't save it without layers apparently either as it hangs and hangs eventually stopping. Other web maps that do not include this layer do not seem to produce the behavior so I assume it has something to do with the high number of layers in this service (30+). It's odd since we've only run into problems attempting to update it today with recent change requests. No issues like this have been experienced prior.
TDLR: The attribute list for search by layer configuration won't update to show the attributes of the new layer selected.
