Trying again to publish Survey123 Form

[SueBoelk2]

We keep getting 'The custom feature service submission_url is not compatible with this survey and Table SDE.sample_chill_water not found. 

Have gone to check that all related tables appear in Layer Properties.

Have added Global IDs using the Geoprocessing Tool as it wasn't being detected when published to webmap.

When we get the sample_chill water to appear another related sample_well_water table disappears.

When we get both the related tables to appear, we get Error: Supports ApplyEdits With Global Ids: false appears.

We've tried deleting and renaming the related tables but the same errors keep happening over and over.

Crazy!

Thanks for any input.

[VenkataKondepati]

Hi,

The buffer geometry step is failing due to how the list is accessed in your script. The error list indices must be integers or slices usually means you’re treating a list like a dictionary.

Quick suggestion: double-check how you're extracting geometry from buffer_result[0]. Sometimes it returns a list of dicts, so accessing .get() may fail.

Also make sure your geometry structure passed into arcgis.geometry.buffer() is valid — especially with 4326 WGS84; try projecting to 3857 before buffering.

Regards,

Venkat

[SueBoelk2]

Thanks Venkat-We've gotten through this problem as it is error after error  but are encountering another issue with globalid: 

[VenkataKondepati]

The error you're encountering—“Unsupported relationship type esriFieldTypeGlobalID in key field GlobalID for table GlobalID”—is indicative of a misconfiguration in the way your related table is defined within the referenced feature service. Specifically, Survey123 requires a GlobalID-to-GUID relationship, not a GlobalID-to-GlobalID setup. This requirement stems from how Survey123 maps parent-child relationships when using the submission_url workflow.

To resolve this:

1. Verify that all involved feature classes and tables have Global IDs enabled. Use the Add Global IDs tool in ArcGIS Pro before publishing your service.

2. Ensure the relationship class is configured as:

   • Origin Primary Key: GlobalID

   • Destination Foreign Key: GUID (must be a field of type GUID, not GlobalID)

3. Confirm that the relationship class is correctly registered as part of the service schema before publishing. It should appear in the service definition and in ArcGIS Online or Enterprise as a related table.

4. Validate your service by loading its REST endpoint and confirming:

   • supportsApplyEditsWithGlobalIds = true

   • Each related table has an accessible endpoint and is part of the same FeatureServer.

You’ll need to republish the service if the current configuration violates these constraints. 

[MichaelTorbett]

@SueBoelk2 have you tried removing  the "SDE." out of your table names (line 30&38) in your xlsx form? Just have the names as 'sample_chill_water' and 'sample_well_water'.  Also try removing it from your Geopoint name on line 7 as well.  

[SueBoelk2]

Thanks Michael- We've got through the above mentioned problem/error but are getting other bizarre errors upon errors:

Thanks for your response.

[MichaelTorbett]

Interesting. Is you relationship class a composite relationship with the primary key being a globalID field  and the foreign key GUID field?