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.
