Skip to main content
  • EN

Having an issue using a FeatureWriter with the following parameters (see screenshot):

  1. Feature Operation = fme_db_operation
  2. Table Handling = Use Existing
  3. Update Spatial Column(s): No
  4. Row Selection = WHERE clause

 

2021-01-14_13-31-09 

I have features coming into the FeatureWriter that are both fme_db_operation INSERT and UPDATE (see 2nd screenshot). My understanding of the Update Spatial Column(s) parameter is based on the help that states "Update Spatial Column(s) is a writer format parameter that is in effect only when the feature operation for a feature is Update".

 

2021-01-14_13-49-41 

However, with this set to No, my Inserts don't get geometry (writing to ArcSDE) while my Updates do. With it set to Yes, my Inserts do get geometry but my Update geometries are nulled out (not good!). I have a temporary workaround using two FeatureWriters (one for Updates and one for Inserts) but doesn't this defeat the fme_db_operation option?

 

Am I doing something wrong here or any other suggestions? My goal is for the Inserts to have geometry and attributes inserted into the geodatabase while the Updates only contain attribute updates and the existing geometry in the geodatabase is not updated. My workaround mentioned above works in this scenario but I'd really like to only use one FeatureWriter.

 

Side note - using the WHERE clause for Row Selection, I have seen records not find a match but come out the Feature Type port but without any indication that it didn't match. I thought it was supposed to get rejected or something?

I think this is due to versioning. Do you get the same results using the Esri Geodatabase (ArcSDE Geodb) writer? Read https://docs.safe.com/fme/2020.2/html/FME_Desktop_Documentation/FME_ReadersWriters/geodatabase/GEODATABASE_SDE_writer.htm it may give you better insight.

I think this is due to versioning. Do you get the same results using the Esri Geodatabase (ArcSDE Geodb) writer? Read https://docs.safe.com/fme/2020.2/html/FME_Desktop_Documentation/FME_ReadersWriters/geodatabase/GEODATABASE_SDE_writer.htm it may give you better insight.

Yes - same results using ArcSDE Geodb writer. I'm writing directly to default using a versioned edit session.

@Jon Atwood​  I couldn't reproduce the issue on file geodb. I'll test on ArcSDE. I've attached my test workspace.

@Jon Atwood​ I had another go against the AecSDE Geodb writer and I couldn't reproduce the issue that you've flagged. I this workspace I'm creating 5m buffers around the original points. Updates & Inserts have a 10m buffer. I've set the writer to Update Spatial Columns = No. So the Inserts should insert with a 10m buffer but the updates should not change the original geometry which is 5m. This seems to be working OK.

I'm using FME 2020.2.2. 64bit and have ArcGIS Pro 2.9 installed.

imageIn the image I have marked:

  • Green UPDATE featureID = 2434
  • Purple INSERT featureID = 9100
  • Yellow Original featureID = 429

I've attached my test workspace. Hopefully you can see the difference in the configuration between this and your workspace.

@Jon Atwood​ I had another go against the AecSDE Geodb writer and I couldn't reproduce the issue that you've flagged. I this workspace I'm creating 5m buffers around the original points. Updates & Inserts have a 10m buffer. I've set the writer to Update Spatial Columns = No. So the Inserts should insert with a 10m buffer but the updates should not change the original geometry which is 5m. This seems to be working OK.

I'm using FME 2020.2.2. 64bit and have ArcGIS Pro 2.9 installed.

imageIn the image I have marked:

  • Green UPDATE featureID = 2434
  • Purple INSERT featureID = 9100
  • Yellow Original featureID = 429

I've attached my test workspace. Hopefully you can see the difference in the configuration between this and your workspace.

@Mark Stoakes​ thanks for looking into this. I was originally using FME 2019.0.0.0 (20190328 - Build 19238 - WIN64 - Data Interoperability for ArcGIS Pro) and decided to upgrade to the latest Data Interop version which is 2020.2.0.0 (20201027 - Build 20787 - WIN64) to see if that changed anything.

 

After upgrading and without changing anything in the workbench, everything worked as expected ( my inserts received geometry while the updates did not). Guess it was a bug in FME 2019.0.0.0?

 

Lastly, every time I close FME I get this error message. Everything seems to be fine but just not sure what is causing this to occur every time I close. Thoughts?

 

2021-01-19_11-25-24 

 

Reply


Community Stats

30,418
Posts
115,549
Replies
38,226
Members
Terms & ConditionsCookie settings
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.