Skip to main content
Solved

Geometry Error when Updating SDE Table

  • March 19, 2026
  • 1 reply
  • 29 views
laurensdelfland
Contributor
Forum|alt.badge.img+9

I have the exact same issue as is described here: 

That topic is closed, so I'm starting a new one over here. 

I got the error “Check the geometry of such feature is valid and is not too small for the resolution”, while updating a feature. 

I use FME Form and Flow 2025.1.2 and ArcGIS Pro 3.3.1 with ArcGIS Enterprise 11.3.

At first I also thought the issue only occurred in FME Flow, not in FME Form. But now I'm checking the issue again and it is also in Form.

In my case I use the ChangeDetector to check if the feature exists and if so if it is changed. If it existed and is changed, I'm also using the Update Mode in a FeatureWriter. I tested with not updating the spatial column, but that didn't make any difference. I still got the error. And I am positive the geometry didn't even change: setting the ChangeDetector to only check geometry sends the feature to the Unchanged port.

I don't really understand the solution in the other topic, but it seems I have to delete some data. But that sort of defies the whole point of the ChangeDetector and the workspace in general.

Best answer by laurensdelfland

I solved the issue. 

There was an attribute rule active on this feature class (https://community.esri.com/t5/attribute-rules-questions/attribute-rule-constraint-combining-getuser-third/m-p/1691509) .

That attribute rule requires the user that makes the edit, to be logged on to Portal. This user is not, which causes the update to fail. The error message is quite confusing, because it had nothing to do with geometry of the feature.

1 reply

laurensdelfland
Contributor
Forum|alt.badge.img+9
  • laurensdelflandContributor
  • Author
  • Contributor
  • Best Answer
  • March 19, 2026

I solved the issue. 

There was an attribute rule active on this feature class (https://community.esri.com/t5/attribute-rules-questions/attribute-rule-constraint-combining-getuser-third/m-p/1691509) .

That attribute rule requires the user that makes the edit, to be logged on to Portal. This user is not, which causes the update to fail. The error message is quite confusing, because it had nothing to do with geometry of the feature.

    Community Stats

    32,386
    Posts
    123,082
    Replies
    40,472
    Members
    Terms & ConditionsCookie settingsAccessibility statement
    A product of
    Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.