topic Re: Map extent wrong on Dashboards in ArcGIS Dashboards Questions

Map extent wrong on Dashboards

MarkCooper5 — Thu, 07 May 2020 12:46:29 GMT

I have got a map in a new dashboard I have set up and it is not using the extent from the webmap. Is there a different place this needs to be set as I cannot find it? At the moment it appears to be using the whole of Europe, which is not the map, organisation or organisation region extent.

Thanks

Mark

Re: Map extent wrong on Dashboards

DerekLaw — Sun, 17 May 2020 16:48:37 GMT

Hi Mark,

> I have got a map in a new dashboard I have set up and it is not using the extent from the webmap.

Are you using ArcGIS Dashboards in ArcGIS Online or in ArcGIS Enterprise? If the latter, which release? I'm not currently aware of any issues with dashboard not honoring the map extent of a web map in ArcGIS Online.

Re: Map extent wrong on Dashboards

DerekPhyn — Tue, 13 Oct 2020 01:58:54 GMT

I've also had this problem in ArcGIS Online. Default webmap extent is just for part of New Zealand but in the dashboard when I open it or select/unselect items in the dashboard the map extent keeps reverting to a huge part of the South Pacific. Default Extent and Bookmarks is checked on in the Dashboard map settings. I suspect there must be a default extent for one of the contextual feature layers I am using in the webmap that is set for a very large area and while the webmap honours the default extent I set up the dashboard will default to the largest extent of any layers used in the webmap? Have not had this issue with other dashboards before. Just this one.

Re: Map extent wrong on Dashboards

Anonymous User — Wed, 14 Oct 2020 16:01:59 GMT

I'm also having this issue

Re: Map extent wrong on Dashboards

CarolineBroughton — Tue, 23 Mar 2021 11:59:41 GMT

This is still an issue several months on. It doesn't consistently happen for me so I assume it is a bug. Is Esri aware of this issue?

Re: Map extent wrong on Dashboards

NO — Wed, 05 May 2021 15:31:23 GMT

I am also having this same issue, on AGOL dashboard.

Re: Map extent wrong on Dashboards

GlasgowGISGlasgowCityCouncil — Fri, 04 Jun 2021 10:32:59 GMT

I am also having this issue

Re: Map extent wrong on Dashboards

Anonymous User — Thu, 01 Jul 2021 00:32:44 GMT

We've got the same problem and have upgraded to Portal 10.8.1 (from 10.6.1) and it's still present, but appears to only be an issue for our own Vector Tile basemaps.

A few things I've noticed:

we have a basemaps group with Esri 102100 and NZTM 2193 basemaps in it. Dashboard isn't able to interchange between them
If the basemap is set to a NZTM 2193 basemap the following error appears on loading the dashboard:

When testing various things, in 10.8.1 when I set the Organization -> Map Defaults -> Default Extent, update the extent values, save it and get the "Default extent updated successfully" message, if I then refresh the page or go out of settings it defaults back to:

Is there anywhere I can manually override it?

Thanks

Re: Map extent wrong on Dashboards

Anonymous User — Tue, 01 Mar 2022 23:01:14 GMT

Apparently this is a known bug https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEzMzUyMA== which won't be fixed for a while.

Re: Map extent wrong on Dashboards

Anonymous User — Tue, 01 Mar 2022 22:24:05 GMT

Has any progress been made on this issue? It is now nearly 2 years since it was reported in this string and I am still having the problem as stated by Mark. A resolution would be greatly appreciated.

Re: Map extent wrong on Dashboards

EulessNick — Wed, 23 Mar 2022 15:57:42 GMT

I'm getting the same issue - and it looks like there are two things contributing to this. First is the issue discussed above about the projections ... the other is the default base map that AGOL used for my map, which is what ddefines the projection in a web map. It automatically used the World Street Map and has a note next to it saying that this basemap has been depricated (so why is it the default). When I changed to a newer basemap the issue with holding the extent in my dashboard went away because apparently the new basemaps use the acceptable projection. You could also make your own basemap using one of the projections WKID 102100 or WKID 4326 (which are an updated Web Mercator) and set that as your map's basemap. That will also fix the problem.