Hello, first of all excuse my English, oh, it is being passed through a translator because I only speak Spanish. The problem I see in this widget is that to now make it work it becomes crazy with a locator that has to make a view and then put it in the enterprise from ago to use it and it seems totally crazy to me when this worked well in Web App Builder , or almost perfect.
Let me explain if in the Web App you put the code of your country and then said that it was restricted to the zoom of the map view extension, it already worked well, it is true that I also propose that this be changed so that you choose to configure it by the extension You want the locator to work because in the Web App, if you get too close to something, it no longer looks for the street in the work area because it is not within that zoom, which I consider an error.
And it is as simple as telling them that it is a window with the entire study area that they have to locate and you can be at a scale of 1:2500 on the other side of that window and it will continue working and looking for directions well. This would be ideal.
But with the Experience everything is more complicated since it requires you to create the happy dweb view. You have to keep in mind that now with the possibility of analysis someone can do reverse localization and that is credits and this is not to place points, we just want to use it so that look for the street, in addition to the fact that you must make so many public locator views in AGOL to take, for example, the Enterprise Portal in order to make the extension window for each project and something that was tremendously simple in Web App Builder with the except that you should also be able to search the entire length of a window around the data being studied or represented.
