Search Widget connected to locators responds differently from one web application to another

[HunterKey]

We are using EB Developers 1.18 and have a series of applications with a search widget that utilizes three locators (Address, PIN, Owner). They are configured to zoom to the location of the first selection and place a custom pin on the location. All but one work as expected. 

I have placed the configurations of working search widgets beside the non-working ones and can not identify the discrepancy. 

The non-working search widget successfully responds to the first address submitted when opening the app. On the second address request within a session, the address will zoom to the location, but not show a pin, and open a default address locator pop-up. There is no option to "Show on Map" for "Record selection Changes", but I did not have to do so in the other successful Search widgets. 

I have a workaround of using a filter to customize an action to use the locator to trigger a selection of the underlying parcel layer, but would prefer to fix the underlying problem that affects the search widget. 

[ShengdiZhang]

Hi @HunterKey ,

Did you configure the message action "Records Created — Show on Map" on the search widget?

Regards,

Shengdi

[HunterKey]

Hi @shengjSheng 

I did, 

I ended up rebuilding the entire application off of a template from one of the working locators. A bit of a pain as I had an intensive Query Widget with options to search 12 different layers with various queries for each feature class. 

I can only Chaulk it up to possibly a corrupted build? I was working on my client side Experience Builder Developers addition. I could not see any thing different in the configuration of the two applications. One worked and one did not, so I am chalking it up to a wonky developer folder for that build? It added a day to the build but it is resolved, by building it off a template from the successfully working Search Widget application.