topic Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer in ArcGIS Field Maps Questions

Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

BrennanSmith1 — Wed, 06 Apr 2022 17:58:13 GMT

I am following the instructions in ESRI's Inspection Workflows YouTube video series. I am using ArcGIS Pro 2.9 and Enterprise Portal 10.9. My 'Join Features' layer is functioning correctly in the webmap, but will not load in Field Maps, with the following error:

Map: Hydrant Inspections Webmap
Layer: Recent_Hydrant_Inspections
Domain: ARCGIS_RUNTIME
Code: 3047
Description: Geodatabase duplicate field not allowed.

The issue is that both the feature layer (Hydrants) and related table (Inspections) contain a GlobalID field. When I perform a Join Features (so we can symbolize on most recent inspection), the resulting layer contains two GlobalID fields named 'globalid' and 'globalid_1649266887779'. I can't find any way to remove one of these fields or resolve the issue.

How is it possible to view a 'Join Features' layer in Field Maps? Why did it work in Eric's demo but not in my environment?

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

AndreasB — Fri, 08 Apr 2022 11:11:27 GMT

@BrennanSmith1 Did you already found a workaround for this issue?

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

BrennanSmith1 — Fri, 08 Apr 2022 11:45:57 GMT

Unfortunately no

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

AndreasB — Wed, 20 Apr 2022 07:53:27 GMT

Bump

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

Kristofer — Thu, 28 Apr 2022 05:13:11 GMT

Hi Brennan Smith,

I had also the similar issue but now with the below given tricks we can resolve this issue.

First, Remove the Global ID from the Layer & add a new field in this layer with different name (not Global ID) and specify the data type as GUID.

When you perform the analysis join features, resulting layer will be only one global id field.

Regards,

Sunita

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

BrennanSmith1 — Wed, 15 Jun 2022 15:39:37 GMT

Update: I worked with ESRI and this is now a known bug with our Enterprise (BUG-000148852). Hopefully they patch it soon.

Sunita, thanks for the advice, but unfortunately we can't remove or rename globalID fields. And because of how we will use the data layers, we need 'Supports applyEdits with GlobalIDs' to be True.

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

XV__ — Thu, 23 Mar 2023 23:12:53 GMT

Hi @BrennanSmith1 , interested if this has ever been resolved. Facing the same bug.

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

BrennanSmith1 — Fri, 24 Mar 2023 11:33:57 GMT

Unfortunately, the bug has not been addressed yet. Its status is listed as 'Under Consideration'. My workaround has been to add a "recent inspection date" field to my feature class, and run a script every night that updates this value. It is far from ideal, and doesn't instantaneously update the labels and symbology, but it's something...

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

StaceyCurry1 — Thu, 30 Mar 2023 19:10:59 GMT

Bump, I'm having the same issue!

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

Key — Mon, 14 Oct 2024 00:09:04 GMT

Same exact issue. Enterprise version 10.9.1

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

SebFischer — Tue, 04 Feb 2025 11:39:29 GMT

This is still relevant - I am running into the same problem trying to set up an inspection workflow in ArcGIS Enterprise 11.1.

It seems to me that if you don't need offline capabilities you can set up your related tables without a GlobalID field to avoid this error. But if your workflow requires the related tables to be part of an Offline Map Area in FieldMap then the GlobalIDs are required and you can't add a Joined Hosted Feature Layer View to the Fieldmap because of the mentioned BUG.

Edit: GlobalIDs are also required for Synchronization capabilities

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

BrennanSmith1 — Tue, 04 Feb 2025 14:19:23 GMT

Sorry to see so many others having this issue still. We recently updated to enterprise 11.3 and the issue is not resolved, and the bug is still 'Under Consideration'. I'm hopeful that taking the entire dataset out of hosted feature layers and into an enterprise gdb with views will let me get the functionality. I will report back if I ever get something working. In the meantime, here's an very stripped down example script you can run to populate a recent inspection date field in the hosted feature layer.

import arcpy # sign into portal arcpy.SignInToPortal(r"https://portalURL",'username', 'password') arcpy.env.addOutputsToMap = False # Load in related table related_table = arcpy.management.MakeTableView(r"URL-to-rest-services/FeatureServer/1",'related_table') # Loop through and populate dictionaries of most recent inspection date # Update inspectiondate field name as needed d_recent = {} with arcpy.da.SearchCursor(related_table,['globalid','inspectiondate'],sql_clause=(None, "ORDER BY inspectiondate DESC")) as cursor: for row in cursor: # add to dict for most recent insp only if row[0] not in d_recent.keys(): d_recent[row[0]] = row[1] # get only features that have related records guids = list(d_recent.keys()) query = "GlobalID IN ({:s})".format(','.join(f"'{x}'" for x in guids)) features = arcpy.management.MakeFeatureLayer(r"URL-to-rest-services/FeatureServer/0",'features',query) # loop through and update with arcpy.da.UpdateCursor(features,['globalid','recent_insp_date']) as cursor: for row in cursor: if row[1] != d_recent[row[0]]: print('Feature {} recently inspected on {}'.format(row[0],d_recent[row[0]])) row[1] = d_recent[row[0]] cursor.updateRow(row)

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

dolson_farmington — Wed, 05 Feb 2025 19:08:57 GMT

It is odd to me that this is still an issue with no straightforward workaround years later. How are other agencies able to create a survey that requires a one to many relationship where Supports applyEdits with GlobalIDs' is True (i.e. literally any dataset that needs routine inspection or maintenance....trees, catch basins, storm ponds, outfalls, etc etc etc etc)?

Am I missing something? Isn't this a basic necessity for any business/government conducting repeated surveys on static features?

Had a support call in which I was told there wasn't a way around it, but that it doesn't appear to be an issue in ArcGIS Online. For the amount we pay for Enterprise, this functionality should be one of the more basic requirements.

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

PTW — Wed, 19 Feb 2025 23:11:35 GMT

I am also running into this problem and I would like to find a solution. I had everything working with AGOL however after switching to Enterprise I am now receiving the error message:

Domain: com.esri.arcgis.runtime.error Code: 3047 Description: Geodatabase duplicate field not allowed.

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

Bertodiem — Tue, 04 Mar 2025 20:03:18 GMT

I reported this bug two years ago in version 10.9. and it is frustrating that in 11.3 this bug is still present.

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

Bertodiem — Fri, 21 Mar 2025 21:20:10 GMT

Here are the steps we followed to resolve the issue:

1. Access the rest endpoint of the join hosted feature layer view in Portal for ArcGIS : First, navigate to the Portal for ArcGIS and open the hosted view layer that is causing the problem. Modify the rest URL adding the word "admin". (Example show below)

2. Update Service Definition : Edit the join features service definition configuration to ensure there are no duplicate field names. This step is crucial as the error message "Geodatabase duplicate field not allowed" is triggered by these duplicates. You should change the visible variable to false and name the globalid field of the related table that repeats. There should only be one globalid field in the definition file.

3. Save Changes: After making the necessary adjustments, save the changes and refresh the hosted view layer

4. Test in Field Maps: Open ArcGIS Field Maps and load the hosted view layer. You should now be able to access the layer without encountering the error message.

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

Bertodiem — Fri, 21 Mar 2025 21:22:20 GMT

I just posted a workaround. Regards

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

Bertodiem — Fri, 21 Mar 2025 21:22:58 GMT

I just posted a workaround. Regards

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

Bertodiem — Fri, 21 Mar 2025 21:24:39 GMT

I just posted a workaround. Regards

Re: Map Layer Failed to Load (3047 duplicate field) - Inspection Workflows and Join Features layer

BrennanSmith1 — Wed, 08 Oct 2025 18:09:36 GMT

Thank you @Bertodiem for this workaround! I haven't deployed it with my main app yet, but it did work in my testing environment. To clarify what you said for others who may have less experience using this approach:

Make sure you are at the URL of the layer and not the feature server. The layer URL will end in "/0". It will look something like this, where the red text is specific to your configuration.
- https://enterprisedomain.org/servername/rest/services/Hosted/JoinFeaturesName/FeatureServer/0
Insert "admin" into the URL between rest and services
- https://enterprisedomain.org/servername/rest/admin/services/Hosted/JoinFeaturesName/FeatureServer/0
Scroll down and make note of the second globalid field, the one with a bunch of random numbers at the end. I believe it will always be the second-to-last field. In my case it was "globalid_1649266887779".
At the bottom of the page, click the Update Definition hyperlink
Change the format to JSON. Use the following text as input, updating the globalid field to match yours

{ "fields":[ { "visible":false, "name":"globalid_1649266887779" } ] }

Click the updateDefinition button. You will hopefully see "success": true

Note that if you are using this globalid field for other applications (e.g., a dashboard where you use this field to count unique entries), it might break something, I haven't looked into that yet.