Currently we have an FME Script for that refreshes 1 ESRI Geodatabase to another (i.e. a direct copy). The problem is when there's an error on just one feature class, the entire workspace fails. Is there a way to bypass any errors and continue with the translation. We want to use a simpler way i.e. not validate all of the fields whenever there's an error encountered (i.e. not use the Tester / AttributeValidator). Can anyone please suggest of the most efficient way to do this?
Question
FME 2016 Bypass error and continue
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.
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.
+21- Safer
Hi @azajarc
If you are doing a 'Direct copy' you might find that the PATH reader coupled with a Filecopy writer is a better method. This is more akin to a Copy/Paste. It should cut down on reading and writing and will not throw errors if there are bad date. Here's an example of someone trying to do something similar: https://knowledge.safe.com/questions/35366/using-filecopy-writer-to-move-fgdb-source-folder-g.html