Dashboard issues since update

05-18-2021 11:10 AM
Labels (2)
by Anonymous User
Not applicable

It was brought to my attention from a colleague that there may be an issue with Dashboards since the April update. Two in particular have surfaced;

  1. Load times have greatly increased on one dashboard. In the following dashboard there is a serial chart in the top right corner. Prior to the update this loaded rather quickly but now, at least on our network, the load time is taking way too long. I'm not sure if it is our network or if it is on Esri's end. Here is a link to the dashboard, https://usfs.maps.arcgis.com/apps/dashboards/e8eefa0094e24af6a290db37dccdde32.
  2. It appears in two dashboards that once you use URL parameters a layer disappears and makes the dashboard unusable. I'm having the colleague check to see if the parameters are configured correctly but prior to the update they were working correctly. Here are two links for each dashboard. One is for the dashboard alone and the next would be with a URL parameter applied.
    1. https://usfs.maps.arcgis.com/apps/dashboards/e8eefa0094e24af6a290db37dccdde32
    2. https://usfs.maps.arcgis.com/apps/dashboards/e8eefa0094e24af6a290db37dccdde32#state=ia
    3. https://usfs.maps.arcgis.com/apps/dashboards/aac8183798ee4375bf25f4a917c8195c
    4. https://usfs.maps.arcgis.com/apps/dashboards/aac8183798ee4375bf25f4a917c8195c#state=ia

Oddly, he also has an Operations Dashboard that seems to be unaffected by the update. Is there a difference between Dashboards and Operations Dashboards? Here are links for a dashboard as an example,

  1. https://usfs.maps.arcgis.com/apps/opsdashboard/index.html#/557046926a6d4ef5b5fad67997f9ae10
  2. https://usfs.maps.arcgis.com/apps/opsdashboard/index.html#/557046926a6d4ef5b5fad67997f9ae10?state=ia

Thank you for your help and explanations!

Tags (3)
1 Reply
New Contributor III

We have had issues as well with the new Ops Dashboard, where the Category Selector was not functioning properly.  After weeks of looking into this and pulling our hair out I was able to identify it was an issue with the spatial reference of the rest services the Category Selector was referencing.  Once we set the service spatial reference to Web Mercator it started to magically work.  I assume there is some requirement to use Web Mercator in the code, we have a ESRI ticket in and asked to have this logged as a bug.  I really don't want to have to update all my services to fix this issue.

0 Kudos