Skip to main content
Question

Updating feature class in FGDB

  • February 11, 2019
  • 3 replies
  • 194 views

gisuser
Participant
Forum|alt.badge.img+4

Hi FME Experts,

 

I have F.C and we received new data for the same F.C

it contains 3 types of update:

- update on the attribute level.

- Update on the geometry level.

- Add new data.

I am trying the insert the new data into the main destination, I tried the update\\insert feature operation with truncate data but it does not work.

there is a way to do this?

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.

3 replies

andreaatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • 444 replies
  • February 12, 2019

Hi @gisuser,

I think the best solution here would be to use fme_db_operation to specify the database operation to preform for writing to the same feature class in a File Geodatabase. The writer feature type parameter "Feature Operation" should be set to fme_db_operation. You will want to have each feature have the attribute fme_db_operation with values of either: UPDATE/INSERT/DELETE.

There are a couple of tutorials for how you can filter the features to determine what operation is needed for the feature. Here is one tutorial for filtering features and setting and here is another tutorial using change detection to set fme_db_operation.

Hope the tutorials help!

- Andrea


gisuser
Participant
Forum|alt.badge.img+4
  • Author
  • Participant
  • 19 replies
  • February 12, 2019

Hi @gisuser,

I think the best solution here would be to use fme_db_operation to specify the database operation to preform for writing to the same feature class in a File Geodatabase. The writer feature type parameter "Feature Operation" should be set to fme_db_operation. You will want to have each feature have the attribute fme_db_operation with values of either: UPDATE/INSERT/DELETE.

There are a couple of tutorials for how you can filter the features to determine what operation is needed for the feature. Here is one tutorial for filtering features and setting and here is another tutorial using change detection to set fme_db_operation.

Hope the tutorials help!

- Andrea

Thank you @AndreaAtSafe

it was so helpful, but I still have an issue with the deleted port from UpdateDetector , it gives an error when I add it in the writer.

 

I guess the reason is that this F.C has a relationship with an external table, there is a way to do that without break the relationship?


andreaatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • 444 replies
  • February 12, 2019

Thank you @AndreaAtSafe

it was so helpful, but I still have an issue with the deleted port from UpdateDetector , it gives an error when I add it in the writer.

 

I guess the reason is that this F.C has a relationship with an external table, there is a way to do that without break the relationship?

Glad it was helpful @gisuser!

I believe if we were to delete a feature from a feature class, the relationship would also be deleted without an issue.

Are you able to share the log file/error message you are receiving as well as your workspace (saved as a template to include the source data if possible)?