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; } } }

Update survey using existing feature service

BrianHiller

When trying to publish an update to a survey that is connected to an existing feature service using the submission_URL setting, I am now getting an error from Survey123 Connect that says the Feature service information is unavailable.

Has something changed with the most recent update to ArcGIS Online that prevents using an existing feature service with Survey123 as before? Here is the error message that I receive.

Find more posts tagged with

Accepted answers

All comments

SMH-Rio

I also had this problem, but I found the solution (actually, the error was mine 🤐).

I usually point the submission_url directly to the layer's service URL, rather than in the standard "https://www.arcgis.com/sharing/rest/content/items/ITEM_ID" format.

However, entering the URL was also passing the layer's index within the service, which was causing the error.

Incorrect: https://services3.arcgis.com/bpW2aXmRSOnKTBmc/arcgis/rest/services/test/FeatureServer/0

Correct: https://services3.arcgis.com/bpW2aXmRSOnKTBmc/arcgis/rest/services/test/FeatureServer

Hope this helps.

Wilson_Marc

Hi @JohnWatson_EBA

Did you find a solution for this issue? I am currently dealing with the same problem and it sounds like we have the same setup. This configuration has worked for me in the past, so I am not sure what needs to be done this time.

ahargreaves_FW

Hi @JamesTedrick

I have a very similar issue that I'm still unable to resolve despite following the work around you suggest above. Here's my setup:

FeatureService1 in AGOL, shared only Org wide.
FeatureView1 is a view of the above Feature Service, with certain sensitive fields omitted, shared publicly.
Public facing Survey hosted in AGOL. This uses FeatureView1 via a submission URL.
FeatureService1 is then brought back into Enterprise using embedded credentials. Let's call this FeatureService2.

Presently we edit FeatureService2 via a WAB and it behaves like a perfectly normal service. But we want to make a Survey within Enterprise that allows for edits to FeatureService2 instead. However:

When I try to make a new survey in Enterprise using FeatureService2 Survey123 Connect never actually makes it, it just spins forever.
If I make a blank survey and then attempt to manually set the submission URL to FeatureService2 I get this:

FeatureService2 operates as a perfectly normal feature service with regard to all other aspects of the Enterprise; I can add it into maps, I can edit via a WAB app etc. Therefore why can I not create a survey within Enterprise that writes back to this Feature Service (which is really an AGOL Feature Service accessed via embedded credentials)?

It is only shared with the org. So when I created the feature layer in AGOL from the service in Portal, I embedded the credentials on that layer. The service in Portal is shared with the org and the survey items and the feature layer are all shared with the AGOL org as well.

JamesTedrick

Hi @JohnWatson_EBA ,

What is the sharing of the service that was published to ArcGIS Enterprise? If it is shared to everyone, it needs to be secured. The feature layer item in AGOL referencing it would need to embed credentials to access it. Otherwise, Survey123 will attempt to communicate with the feature service directly, which is in a different identity management; this will result in invalid tokens being sent to the feature service.

JohnWatson_EBA

Sure. I created the survey from scratch in Connect, v3.12.232, published it up to AGOL as a hosted feature layer. Submitted a survey and downloaded the layer as a fGDB locally, then exported the FC to the client's .sde database. Used ArcMap to then publish the .sde FC as a service in Portal. Created a feature layer item in AGOL pointing to the feature service in Portal and attempted to use that item ID in the survey to republish.
Thanks for getting back to me so quickly, I really appreciate it.

JamesTedrick

Hi @JohnWatson_EBA ,

Can you provide more details on the publishing setup? The feature layer is in AGOL? If so, what is the sharing setting on it? In general, Survey123 expects the feature service to reside on the same ArcGIS Enterprise as the form. There is a way around this, which is documented as they work-around to support stand-alone ArcGIS Server services.

JohnWatson_EBA

Hi @JamesTedrick - I actually just came across this as well, and I can confirm the service does exist and is visible from the same account that published the survey. I am trying to use a feature layer I created in AGOL from a published feature service in Portal (that is tied to an sde FC), but the survey won't publish. If I create a new feature layer in AGOL using the same fields from the feature service, then I can successfully republish the survey using the submission url to that layer. What gives?

JamesTedrick

Hi Brian,

This appears to very particular to your survey & feature service - you may want to double-check that the feature service exists and is visible from the account that published the survey. I would also go to the item details page of your form item- it should show a link to the feature service URL. Is there anything else about the history of this service/form that could be unique?

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.