Skip to main content
Solved

1019 error with change detector and polygons

  • July 1, 2025
  • 4 replies
  • 44 views
mwoods
Contributor
Forum|alt.badge.img+2

Hi all. I am just trying to do something very basic but keep getting a “1019 error. The specified feature could not be updated or does not exist” when using the update feature writer.

This only happens with polygons and lines/polylines but works fine with points.

The workbench below is taking a polygon boundary dataset from portal, taking a polygon from AGOL putting it through a change detector - whose unique identifier is a name in both features- then updating/inserting/deleting when necessary to essentially make the AGOL layer the same as the portal layer….Or in theory this is what i want it to do.

 

Any help would be much appreciated.

 

 

Best answer by hkingsbury

I’ve been able to replicate your issue.

It appears the way the AGOL Writer is determining which features to update based on either the ObjectID or GlobalId (depending if the writer is set to use Global IDs)
 

 

The error is saying that there isn’t a feature with that ID to update

The error code from the server was '1019' and the message was: 'The specified feature could not be updated or does not exist.'

To retain the value from the AGOL Reader, you can specify the Global/ObjectID field to be preserved on the Updated Output port in the ChangeDetector
 

 

danilo_fme
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

hkingsbury
Celebrity
Forum|alt.badge.img+64
  • hkingsburyCelebrity
  • Celebrity
  • July 1, 2025

How is the feature writer configured?

mwoods
Contributor
Forum|alt.badge.img+2
  • mwoodsContributor
  • Author
  • Contributor
  • July 2, 2025

I have just left it as the standard update settings.

 

 

hkingsbury
Celebrity
Forum|alt.badge.img+64
  • hkingsburyCelebrity
  • Celebrity
  • Best Answer
  • July 2, 2025

I’ve been able to replicate your issue.

It appears the way the AGOL Writer is determining which features to update based on either the ObjectID or GlobalId (depending if the writer is set to use Global IDs)
 

 

The error is saying that there isn’t a feature with that ID to update

The error code from the server was '1019' and the message was: 'The specified feature could not be updated or does not exist.'

To retain the value from the AGOL Reader, you can specify the Global/ObjectID field to be preserved on the Updated Output port in the ChangeDetector
 

 

mwoods
virtualcitymatt
mwoods
Contributor
Forum|alt.badge.img+2
  • mwoodsContributor
  • Author
  • Contributor
  • July 8, 2025

That worked perfectly. That's so frustrating that it was something so simple to change

 You have saved me so much time trying work-arounds and complicated procedures. Its very much appreciated!

hkingsbury

Community Stats

32,128
Posts
121,966
Replies
39,779
Members

Latest FME

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.