The same exact geocoding service is working just fine when using the WAB online but it does not seem to work the same when the developer edition is used - sub-addresses don't seem to work ...
I would appreciate any insight on this topic
Based on technical support from ESRI in order to make our 10.3geocoding service work on any sub address with unit number (apartment) we hadto delete some lines of code in the widget.js file within the search (widget)folder inside the widgets folder of the Web AppBuider application:Server->apps->appID->widgets->Search->Widget.js
Line number 252: delete the localSearchOptions and the commaafter the ….searchInCurrentMapExtent
Can you share a screen shot of your browsers web console error if there is one?
Robert thank you so very much for reading my post and taking the time to ask me for more details - really appreciate your time.
I'm inserting here screen shots with the same exact address searched on three different ways - using the same geocoding service (not externally accessible)
- one is the WAB dev edition
- one is the online version of the WAB
- and the third is the rest interface of the geocoding service used
All work except the WAB dev edition and that is the only one that also throws errors on the console - also inserted here - but it seems like the errors are there no matter if geocoding returns or not any matching results (they show up even when matching results are found and retrieved....)
Sorry there is just not enough info here for me to go on. Is there anything else in the web console that could help me diagnose?
I know Robert - I wish the geocoding service was externally accessible. I really appreciate your time ....
I just opened a case with ESRI and they are trying right now to reproduce the issue - will let you know of our findings on this.
We love your widgets - great work !
Retrieving data ...