nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Editing is not possible because the record specified by the globalId parameter cannot be accessed

CharlieColey123

I have an AGOL ownership based access feature layer view with S123 pointing to it and updating records in Ops Dashboard

https://survey123.arcgis.com/share/0ee2fd67c5104de7923944eb2eac4cfe?mode=edit&globalId={GlobalID}&version=latest

When I create the dashboard it sometimes initially works, but then if i copy an paste the url to another tab it immediately fails. This was all working fine then suddenly stopped

I have cleared out the features and started from empty again but still same problem. Any help gratefully received

Thankyou

Charlie

Find more posts tagged with

Accepted answers

All comments

Marc_Patti

I struggled with this error when trying to load a survey in an embedded widget attached to a list. My issue ended up stemming from the Global ID placeholder, which I was entering incorrectly. The fix was to add the placeholder using the "Data" button, searching for the "Global ID" field, and then clicking to add it into the hyperlink. This ensured that I was calling the placeholder correctly.

Screenshot 2026-06-24 081558.png

JMCM

Hello - I know this topic is old, but here are the troubleshooting steps I used:

1. Try to load the survey without the globalId = {field\GlobalID} parameter

2. Try to load a sample GlobalID from the layer that the survey is based on instead of {field\GlobalID}}

3. If the survey is based on a view layer, update the definition for the view layer (no changes needed, just try it)

4. If you're hosting this survey as embedded content on a Dashboard, make sure the feature layer referenced is the same one the survey is based on - including the exact same view layer, not just the same master layer/data

5. Check to make sure the GlobalID field exists and that all text references to it in the survey are case-sensitive

AndresCastillo

This article is helpful:
https://support.esri.com/en-us/knowledge-base/error-editing-is-not-possible-because-the-record-specif-000028842

For me,

I had to allow the group within my org access to submit survey (under the collaboration tab):

ahargreaves_FW

I am getting this message in an Experience Builder App where I embed a Survey123. As soon as I select a feature on the map the GlobalID is passed to the survey and it loads my results - this is expected behaviour. My question is how can I edit this message to be more user friendly? I need to inform users to select a feature on the map to remove the error.....

carlosreyes_dotca

Hi Charlie,

I think I may have figured out what is the issue. It might have to do something with the editing settings you have configured for your feature layer. I got the same warning message when my users tried to edit an existing survey. For the "What features can editors see?" option, is it "Editors can't see any features, even those they add"? You have to switch it to "Editors can see all features" to allow users to access the globalId field (and include the Update features option) when they want to edit a survey that doesn't belong to them (at least that was the issue for my case). But we also need to make our survey public.

My organization is interested in releasing a public survey, and when you make a survey public, you also have to make the associated feature layer public. I followed the workflow and editing settings that Esri provided to secure the data and ensure that no one could edit or view the data (please see below).

We also have an internal (second) survey, based on the same feature layer from the first survey, to review and approve the surveys submitted. I created a view layer from the original feature layer (to view and edit the layer) and embedded the survey into a dashboard to create a user-friendly application. The application worked perfectly fine for me, but when I shared the application with my teammates to review, they mentioned that they could not edit any surveys since they got the "Editing is not possible because the record specified by the globalId parameter cannot be accessed" message.

After doing a bunch of testing and talking with my team, it finally hit me that the other users can't access the globalId field because of the editing settings (What features can editors see? - Editors can't see any features, even those they add) I configured. By creating a view layer to edit the data from the original feature layer, I thought my users could access the data with no problems. However, I created the internal survey from the feature layer with all the restricted editing settings. Because my account owns the survey and all other associated items, my account can view and edit everything, but not for the other users. Once I updated the "What features can editors see?" option to "Editors can see all features" (and included updating is allowed for the type of editing), my users were able to view and edit existing surveys. However, we need to make the data secure and hidden from the public for our purposes, so the editing settings have to be restricted. To get around that, we created a second view layer and based our internal survey on that view feature service to enable the appropriate editing settings to edit existing surveys.

It looks like everything is working, but I don't know if there are any repercussions (other than deleting the source layer) by creating a survey based on a view layer instead of the source layer.

Please let me know if anyone has done something similar or if you have found another workaround. I am curious to hear other people's thoughts.

Thanks!

Carlos

GaryBowles1

I had a similar issue with a survey embedded in a dashboard and 2 issues were flagged by support. One was having 'jr:choice-name()' function within an equation. The second was using autocomplete for the appearance of a choice list. Our survey was initially created using Connect and stored in Enterprise.

Hope this helps.

--gary

TylerBragg2

Charlie,

I'm having a similar problem, described in my recent thread here.

Not exactly the same, but I have a case with technical support open as we speak. Ultimately, we think my problem may have something to do with the say Survey123 is understanding the URL parameter for the GlobalId. I'm getting a "Failed to Submit" problem using the syntax you described above. We still aren't sure what's going on, but we will get to the bottom of it. I don't know what changed, but my issue seemed to start immediately after the April 13th update of AGOL. When did your start giving you problems?

CharlieColey123

Hi Josh

Thx for getting back to me

latest version

Can't get to bottom of this issue!

Thx

Charlie

jcarlson

Is your survey set to use a specific version, or always use the latest version of S123? We had a few surveys stop working when they were stuck on a legacy version that conflicted with a recent update.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.