Select to view content in your preferred language

Editing survey via dashboard no longer working due to globalId error (after 1.5 years of working fine)

338
8
Jump to solution
11-18-2024 06:38 AM
ShelbyZelonisRoberson
Frequent Contributor

Hi. I have a few dashboards that have embedded surveys in them to edit records in a feature service (registered; published in 11.2 Enterprise). Everything has been working fine with these surveys since I created them in 2023.

This morning, one of my users said they are getting the error "Editing is not possible because the globalId parameter was not provided". I checked the other dashboards I have with similar workflows and all have the same problem. I went through this article and everything is set up properly: https://support.esri.com/en-us/knowledge-base/error-editing-is-not-possible-because-the-record-speci...

NOTHING has changed on my end, but I see that Survey123 had an update last week. I put in a ticket with Esri but they don't have an answer yet. This is impacting very important production work.

@IsmaelChivite  @JamesTedrick any ideas?? 

0 Kudos
1 Solution

Accepted Solutions
ShelbyZelonisRoberson
Frequent Contributor

Fixed it! I don't know WHY this worked, but I decided to overwrite the service (republish), then started and stopped the service. It is working now, for anyone in the future that has a similar problem! 

View solution in original post

0 Kudos
8 Replies
abureaux
MVP Frequent Contributor

You in AGO? If so, this is likely related to a recent update.

And I should probably clarify, but I was referring to the dashboard being made in AGO. There are 3 versions of Experience Builder (And WAB, if you still use that): AGO, Enterprise, Dev. AGO get updates automatically, which can break things sometimes.

0 Kudos
ShelbyZelonisRoberson
Frequent Contributor

Enterprise 11.2, but Survey123 had an update last week that could have impacted this. 

0 Kudos
abureaux
MVP Frequent Contributor

An S123 update shouldn't impact a web map like that. Unless the GID was missing (which seems unlikely). And if you are in Enterprise, your EB/WAB versions are effectively static.

I have a few survey/web map combos that are set up like that, and i used one just 5 minutes ago (not the best picture, but the info is being passed from EB to S123 as it should):

abureaux_0-1731948320839.png

This does seem odd.

0 Kudos
ShelbyZelonisRoberson
Frequent Contributor

Something had to have impacted it. It's the embedded URL that isn't working anymore. The Survey works fine as a standalone. 

 

https://survey123.arcgis.com/share/8f4c1d1517be4154858a418681fa4896?mode=edit&globalId={field/global...

0 Kudos
abureaux
MVP Frequent Contributor

Oh, are you not editing within EB, but instead using a URL to pass the selected point on to the Field App for editing? Okay, that's different, and doesn't really depend on EB.

Can you inspect the link prior to pressing the URL? Does the URL look correct in the web map? Or is it already broken by that point (e.g., the GID isn't in the URL).

0 Kudos
ShelbyZelonisRoberson
Frequent Contributor

I'm editing within Dashboard. Using an Embedded Content widget to pass the URL to the specific Survey123 record. (This is the workflow I've been using for years: https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-embedding-a-survey...)

If I hardcode a globalid into the URL and test in the browser, I get the same error. For example, this gives me the globalid error even though this points to a legit globalid in my feature service: 

https://survey123.arcgis.com/share/8f4c1d1517be4154858a418681fa4896?mode=edit&globalId={9BCC1C8C-171...

Again, all of this has worked fine for years. I'm so confused. 

0 Kudos
ShelbyZelonisRoberson
Frequent Contributor

Fixed it! I don't know WHY this worked, but I decided to overwrite the service (republish), then started and stopped the service. It is working now, for anyone in the future that has a similar problem! 

0 Kudos
abureaux
MVP Frequent Contributor

Glad you got it working again!

That is very strange though, as nothing should have impacted that behaviour.

I have several forms set up that way, so I'll keep a republish in mind if they randomly start acting up.

0 Kudos