Set scale range limits changes map to full extent

MichelleD

In Experience Builder (developer edition), I have several custom basemaps, some vector and some cached to 1,128.  When scale range limits are not set and the map is zoomed in beyond 1,128, if the user selects one of the cached basemaps the map will zoom to the basemap LOD 1,128 (expected).  However, when scale range limits are set and the map is zoomed in beyond 1,128, if the user selects one of the cached basemaps the map zooms all the way out to the full extent as was set in the scale range limit (not the basemap full extent).  This means the user loses the area of interest completely.  Why when scale range limits are set does it not just zoom to 1,128 as it does when scale range limits are not set?

MichelleD

No, not quite.  Map and basemap both have multiple levels.  For example, an experience has multiple basemaps, some basemaps can zoom to level 282, others only to 1,128.  A user zooms into a parcel and is at level 564.  If they switch to a basemap that only goes to 1,128, then the map zooms out to 1,128 still centered on the parcel.  That makes sense because the map is zooming out to the level the basemap can draw, and that is what happens if scale range limits are not set (default).  However, if scale range limits are set, instead of zooming out to 1,128, the map zooms all the way out to 160,000 (or whatever the full extent custom scale range is set to).  So the user has to start all over and search for the parcel again.  If scale range limits are set, it should work just as it does when they are not set, it should stay centered on the parcel and zoom out to 1,128.