Skip to main content

We have a workspace - published in FME Server - that crunches a bunch of data, writes out one or more records to an Excel file, and then kicks off an FMEServerJobSubmitter to a second job that reads in the Excel file to update some features in ArcGIS Online. Our issue is that the second FME Server job fails because the Excel file it is trying to read is still in the process of being written in the first job. How do we ensure the Excel file is done writing in the first job before the second tries to read it? We are running FME Desktop and Server 2016.

 

Thanks,

Aaron

If you have workspace A calling workspace B, the trick is to use an extra workspace C who will call A waiting for the job to terminate and then call B. By doing this, A no longer have to call B by itself.


If you have workspace A calling workspace B, the trick is to use an extra workspace C who will call A waiting for the job to terminate and then call B. By doing this, A no longer have to call B by itself.

Makes sense. That should do the trick. Thanks!

 

 


Reply