Skip to main content
Solved

New ArcGIS Feature Service Writer failing inserts when a globalid field is not exposed in the Writer and Advanced Parameter Use Globalid is set to No

  • January 13, 2026
  • 2 replies
  • 70 views

jakethepainter
Contributor
Forum|alt.badge.img+6

FME 2025.1.3.0 Build 25643

I downloaded the new ArcGIS Feature Service Package and set up a connection using the Esri ArcGIS Online OAuth Web service. 

When I attempt to insert a new feature into an existing AGOL feature service using the default values of the Esri ArcGIS Feature Service format, I get a warning

WARN  |ArcGISFeatureServiceWriter: The field 'GlobalID' has a NotNull constraint, but it is NULL, missing, or empty. Skipping feature...

The feature is not committed but the FeatureWriter or Writer (I tested both) shows success and the number of features written as 1. Without reading through the warnings, I wouldn’t know there was a problem.

Since I’m inserting a feature I don’t have a globalid! And the field is noneditable in the feature service, so it seems like an odd error.

Messing around with the settings I found that if I made sure the GlobalID field was exposed in the User Attributes and in the Advanced Parameters “Use GlobalID” was set to Yes, then the feature would insert. But I don’t understand why this is the case.

If the Use GlobalID is set to Yes and the GlobalID attribute is not exposed, the FeatureWriter fails. That is at least more obvious.

Previously when writing to AGOL feature services I would tend to not expose the noneditable fields (ObjectID, GlobalID, edit tracking fields) to limit the number of warnings logged by FME that fields are noneditable and won’t be updated. 

Is this intentional or a bug?

I reproduced this in a workspace that simply uses a creator to create 1 point feature and then inserts it in my test feature service which I created with no extra fields or anything.

Best answer by desiree_at_safe

Hi ​@jakethepainter! What you’re experiencing might be a slightly different manifestation of what is happening with Global IDs here: 

This issue should be fixed in package v3.19.1 now available on the FME Hub. Let us know if updating the package resolves this issue!

2 replies

desiree_at_safe
Safer
Forum|alt.badge.img+17

Hi ​@jakethepainter! What you’re experiencing might be a slightly different manifestation of what is happening with Global IDs here: 

This issue should be fixed in package v3.19.1 now available on the FME Hub. Let us know if updating the package resolves this issue!


jakethepainter
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • January 15, 2026

Thanks. Updating to v3.19 means that the default parameters of Use Globalids = No and not having the attribute exposed in the User Attributes sucessfully inserts the feature rather than skipping it.

I should note for those who are interested. If the parameter Use Globalids = Yes and the Globalid attribute is not exposed, the translation will fail. It’s a little odd since that parameter doesn’t really apply to an insert operation. So something to look out for if you’re copying writers/featurewriters around with different operations and you are using Globalids otherwise to do updates, for example, so have modified the parameter. Either the Globalid attribute needs to exist in the User Attributes or Use Globalids needs to be set to No, in my testing with the latest package.