GIS Request Management- GIS Activities Dashboard

[ChelseaFraley]

Hello!

Is anyone else experiencing issues with the GIS Activities dashboard freezing and then timing out? We have noticed it happening when we try to update an activity using the Update tab in the right side panel, and also when switching between the View and Satisfaction tabs the right side panel. Therefore we think the issue is isolated to that part of the dashboard configuration.

We are experiencing the same freezing and timing out when we view the GIS Activities dashboard where it sits within the GIS Request Management Center, when we open it as a stand alone dashboard, and when we try to edit the dashboard. It is also occurring in both Chrome and Edge, and while in incognito mode.

Currently it is the only component of the GIS Request Management Solution we are having issues with. 

Thanks for any help!

Chelsea

[DanielWickens]

Hello @ChelseaFraley - This is a known issue that other users are experiencing following last night's AGOL update, and we will be notifying the Dashboard/Survey123 teams. For now, here are the steps to resolve the issue. Kudos to @CoreyUnger and @CierraScriven for helping troubleshoot and outlining detailed steps:

1. Open the GIS Activities Dashboard in edit mode.

2. Copy the dashboard's full URL.

3. Close all tabs and open a fresh browser tab.

4. Open your browser's developer tools (F12 or Ctrl + Shift + I)

5. In the Network tab, click Filter and type 'Survey123' in the textbox.

6. With developer tools still open with the filter set, load the GIS Activities dashboard in edit mode and click on a request and then click the 'Update' tab to trigger the error.

7. In the network tab, look for a request containing the Survey123 item id, your portal's URL, and URL parameters. E.g., https://survey123.arcgis.com/share/{itemid}?portalUrl={portalURL}&mode=edit&globalId={globalid}&fiel...

8. Right click the request and select 'Block request URL' and 'Block request domain'.

9. Open a new browser tab, open developer tools again, and ensure 'Enable network request blocking' is checked on.

10. Reload the dashboard in edit mode, this time the embedded content should not crash.

11. Click the Update embedded content element's configure button, and find the Data > URL setting.

12. In the URL, find '&field:manager=Yes', and remove it. 

13. Click Done, then Save to save your changes.

14. Reload the dashboard to verify the dashboard loads the survey form.

Note: The &field:manager=Yes URL parameter is used to hide/show fields in the form related to program goals, organizational goals, and capabilities. Since you removed this parameter, those fields will remain hidden unless you modify the Survey123 Connect XLS form by removing ${manager}='Yes' from the body::esri::visible cell for the Goals and Capabilities begin group (cell AA32), then saving and publishing your changes.

[ChelseaFraley]

This was very helpful and did fix the problem for us, thank you!

[YvesLeger]

We are also experiencing the same issue.  Hopefully this will be fixed soon.

[DanielWickens]

@YvesLeger - The detailed steps above will resolve the issue, and we also have the issue logged for the Survey123 team to review.

[DanielWickens · Accepted solution]

UPDATE (2/28/25): 

I have an update and a much easier way to fix the issue while also keeping the field:manager=Yes paramater in the URL. 

Turns out the issue is indeed related to using the 'version=latest' URL parameter. By default, we set the GIS Activity survey to use the latest version of Survey123 (3.22), and that is causing the loading issue. 

In the survey's settings, you can change the web app version to use the version the survey was published with (3.20). You can then remove the 'version=latest' parameter from the URL completely, or hardcode 'version=3.20' if you've already republished the survey using a later version.

So the URL will look like this: https://survey123.arcgis.com/share/8a002bd2b2a84355b1ba0a5a15fedb8f?portalUrl=https://localdeploymen...

Please give this a try, and let me know if it works for you. 

Update (2/28/25, 12:53 PM MST) - The Survey123 team is aware of this and has a hotfix in.

Update (3/5/25, 7:12 AM MST) - The Survey123 team resolved the issue with a hotfix last night.

[KassieKM]

EDIT: I had tried the fix yesterday, I reloaded everything again this morning and it seems to be working now. 

This fix alone did not work for me. Do you need to do this in addition the steps above?

[DanielWickens]

@KassieKM - the issue was resolved in a hotfix by the Survey123 team last night. Updating my previous comment.