Hi everyone,
I'm working with FME Form 2025.1 to update features in an ArcGIS Enterprise feature service that uses branch versioning.
I'm using a Feature Service Writer to update existing features based on their GlobalID. The workflow runs successfully, and I'm able to update certain fields without any issues.
However, I've noticed that a few specific fields aren’t retaining the value I'm sending through FME, while other fields are updated successfully using the exact same workflow.
I suspect this is happening because of the attribute rules we have currently set up. The fields I’m unable to update from FME are the same ones that have a corresponding attribute rule.
To make it even weirder, you’d think that with any update (even if from FME), the attribute rules would go into place and start triggering the rules to fill in the other fields we have rules for, but only the fields I’m updating via FME are changed.
The challenge:
-
The feature service is used in a production environment with branch versioning and reconcile/post workflows.
-
Modifying attribute rules requires us to take down and republish the service, which we'd strongly prefer to avoid.
-
I believe that temporarily disabling attribute rules isn't an option without involving our GIS administrator.
-
Because of our attribute rules, when trying to bulk update features that have attribute rules, it basically just runs forever.
My questions:
-
Is there any way to configure the FME Feature Service Writer to update a field without triggering its associated attribute rule?
-
Are there alternative approaches within FME for updating specific attributes in a branch-versioned feature service that might avoid this issue?
-
Has anyone encountered a similar situation where certain fields update successfully through FME but others don't because of attribute rules?
I'm open to using a different transformer, writer configuration, or approach if necessary.
Any suggestions would be appreciated, thank you!!