Skip to main content
Question

Data download NOT outputting file from writer when script continues

  • March 13, 2024
  • 2 replies
  • 220 views

izabreton
Contributor
Forum|alt.badge.img+3

Hi, 

I have a script with 2 choices: download a GDB or make a feature service.  Currently, when I choose to download, the script stops after writing, and if Iopt for making a feature service, it continues after the feature writer. However, I am not getting a URL to download the ZIP file in FME Server Data Download when making the feature service. I have implemented a second writer as a workaround, but I am searching for a more effective solution. Any idea how I can implement that?
Thanks!

2 replies

izabreton
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • 6 replies
  • March 13, 2024

Correction: I am not getting a URL to download the ZIP file in FME Server Data Download when making the feature service or choosing download. 


mattmatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • 108 replies
  • March 18, 2024

Hi @izabreton, please check that:

  1. Your workspace has been registered with the data download service. This can be done when publishing to FME Flow. See https://docs.safe.com/fme/html/FME-Form-Documentation/FME-Form/Workbench/fmeflow-register-workspace.htm
  2. When the workspace was registered with the data download service, the GDB writer was not removed from the list of writers to include in the data download (this is visible when you click ‘Edit’ next to the Data Download service in the final ‘Register Services’ step of the publish wizard in FME Workbench).
  3. When running the workspace on FME Flow, that it is being run on the Data Download service. If the workspace was registered with multiple services, it’s possible it’s not being run on the Data Download service. You can check the job log on FME Flow to see which service the job was run against by searching for the FME_SERVER_REQUEST_URI parameter. For example: 
    --FME_SERVER_REQUEST_URI' `https://myfme.flow/fmedatadownload/Samples/austinDownload.fmw

If you’re still having issues after this, I recommend submitting a case with the workspace .fmw file and job log from FME Flow.