Skip to main content

Hi everyone

 

I have been having some issues with the new ArcGIS feature service writer. When using this writer in combination with a change detector, it doesn't seem to update or insert any of my changed records and i have been getting weird behaviour all over the place. Let me preface this by saying that everything works as expected on the old portal feature service writer, it's when switching to the new feature service writer that weird things start to happen. 

 

Under the advanced parameters I have enabled the following fields to adress the first problem I encountered (namely that the writer no longer seems to care that global id is a read only field and skips it for writing): 

 

Afterwards, I ran into the next set of errors:

All global id's for the update actions are filled and added as an attribute. 

I don't really get what i am doing wrong, but furthermore I really don't understand why the behaviour seems to be so different in the new arcgis feature servicewriter. Why do i have to jump through so many hoops and errors to get something to work that used to work fine in the older writer? Is there a list of changes that I should be aware of when updating to the new writer format? If so, I couldn't find them

Hi ​@mgrupp,

Would you be able to share your workspace (or a screenshot of it at least) so that we can have a deeper look at the issue you are having?

Thanks

Hi ​@mgrupp,

Would you be able to share your workspace (or a screenshot of it at least) so that we can have a deeper look at the issue you are having?

Thanks

Hi pierre,

I have added the workspace as an attachment.

Thanks in advance! :)

Hi ​@mgrupp thanks for providing your workspace! We have filed an internal issue to investigate what is happening (FMEENGINE-88396) and we’ll keep this thread updated with what we find. 

You say that this used to work, so this may not help, but I’ll put a few suggestions below in case:

  • try changing the “Features Per Request” writer parameter to something smaller like 500
  • since the last 500 features failed, see if there’s anything different about the data in those features. 
  • see if this error only happens with one operation, i.e. insert, update, delete. Using fme_db_operation is the most simple in the end but makes it harder to isolate. 

I’m getting a related issue. I’m reading data in via the Feature Service reader, then writing data back via the Feature Service writer. I’ve been able to get the writer to work for updating existing features (attributes changes using “Update”) but haven’t been able to get the writer to work for inserting new records (Insert).

It’s not throwing any errors, in fact it says that features are written successfully. But the new data isn’t present in the dataset. For context, this is referenced/branch versioned SDE data being written to DEFAULT.

Workbench attached.

 

I also agree, that the FeatureService reader/writer seems like it was released before it was fully baked. We’ve run into a few bugs and things that aren’t documented, without cobbling together workarounds from several community posts and threads.

Now I have gotten the writer to Insert new features (I had to make sure “Use Global IDs” and “Preserve Global IDs” were checked under Advanced Options, and insure a field called “GLOBALID” was being passed to the Writer, even though these are newly created features that don’t have a GLOBALID value).

Now the issues is that the features are being created 4000+ miles from where they are supposed to be located. I’m using a Geocoder to generate the location, and the point location looks fine in FME, but in GIS it’s way off. All of this worked fine with the Portal Writer.

Deleted

​@nathanherzog Are you able to provide the latest version of your workspace so that the team can investigate?

Community Stats

32,002
Posts
121,535
Replies
39,619
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.