Skip to main content
Question

File copy Writer -Error on invalid destination parameter not working

  • May 20, 2019
  • 7 replies
  • 94 views

raaaju1990
Contributor
Forum|alt.badge.img+9

I'm using file copy writer to copy gdb from source location to destination. I'm using file copy writer for this. One of the parameters in this writer is Error on invalid destination which I have set it to NO. So, this means that, if there is no valid destination location found, FME should proceed further without terminating the translation (This is according to the documentation). But, this doesn't happen.

 

So, how can I handle the error and proceed further with the translation without terminating it.

 

Could anyone provide some suggestion on 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.

7 replies

pratap
Contributor
Forum|alt.badge.img+12
  • Contributor
  • May 20, 2019

Have you passed the values of all the below attributes...

a. filecopy_source_dataset

b. filecopy_dest_dataset

c. filecopy_dest_filename


raaaju1990
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • May 20, 2019

Have you passed the values of all the below attributes...

a. filecopy_source_dataset

b. filecopy_dest_dataset

c. filecopy_dest_filename

Yes, I have passed and it works fine. But in worst case scenario, suppose the destination location is invalid or not accessible due to any reason, I want the fme to proceed further without terminating the entire process.


pratap
Contributor
Forum|alt.badge.img+12
  • Contributor
  • May 20, 2019

Yes, I have passed and it works fine. But in worst case scenario, suppose the destination location is invalid or not accessible due to any reason, I want the fme to proceed further without terminating the entire process.

To my understanding... If destination folder does not exists then FME will create folder as per the path you have provided


nielsgerrits
VIP
Forum|alt.badge.img+64

Yes, I have passed and it works fine. But in worst case scenario, suppose the destination location is invalid or not accessible due to any reason, I want the fme to proceed further without terminating the entire process.

If the issue is the termination of the entire proces you might want to change your "Rejected Feature Handling" setting from "Terminate Translation" to "Continue Translation".

You can find it in the Navigator under Workspace Parameters, Translation.


raaaju1990
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • May 20, 2019

To my understanding... If destination folder does not exists then FME will create folder as per the path you have provided

Suppose in case, the folder is not accessible or if there any network issue with the shared folders, at that time I want the process to proceed further without copying the files. For this purpose I'm trying to use this option -Error on invalid destination which is available as a parameter in the writer and I have set this to NO


raaaju1990
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • May 20, 2019

If the issue is the termination of the entire proces you might want to change your "Rejected Feature Handling" setting from "Terminate Translation" to "Continue Translation".

You can find it in the Navigator under Workspace Parameters, Translation.

I tried this option. But, not working as expected. Its terminating the translation


jovitaatsafe
Safer
Forum|alt.badge.img+11

Hi @raaaju1990,

I can't seem to reproduce the behavior where the translation terminates due to an invalid destination with "Error on Invalid Destination" set to "No". It seems to work as expected for me, completing successfully, and logging warnings that I need to check my file permissions to write to the destination folder.

Would you be able to share you full logfile and perhaps a sample workspace as well?