Skip to main content
Question

Using published param value in FME Server output filename

  • May 28, 2013
  • 5 replies
  • 96 views

nic_ran
Contributor
Forum|alt.badge.img+16
Hi,

 

this question has been asked previously in the old forum but I couldn't find any answer.

 

 

I have a workspace that writes an Excel file. The destination dataset uses the value of a published parameter to set the output filename.

 

e.g.

 

DEST_DATASET = $(PROSPECT).xls

 

 

When running the workspace on the desktop the replacement works as expected. e.g. the output filename becomes "my_prospect.xls".

 

 

When the workspace is published up to FME Server (2013 sp2) as a data download service the workspace runs but the XLS file returned inside the .zip file is called "$(PROSPECT).xls". ie. no parameter substitution is occuring.

 

 

Does anyone know how to do this?

 

 

thanks,

 

Nic
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.

5 replies

nic_ran
Contributor
Forum|alt.badge.img+16
  • Author
  • Contributor
  • May 28, 2013
Forgot to mention.

 

 

If I use the Job Submitter service then the parameter substitution works as expected. It's the Data Download service that I can't get to work...

nrich_defra
Contributor
Forum|alt.badge.img+6
  • Contributor
  • May 29, 2013
Hello,

 

 

I had the same problem but asked the question in a different way.

 

 

Didn't find a solution for the problem you are describing, but  I did find a way to create a dynamic filename in a workbench registered with the data download service, which is perhaps what you are trying to achieve?

 

 

https://safe.secure.force.com/AnswersQuestionDetail?id=906a0000000clIkAAI

 

 

Regards,

 

Nick

nrich_defra
Contributor
Forum|alt.badge.img+6
  • Contributor
  • May 29, 2013
https://safe.secure.force.com/AnswersQuestionDetail?id=906a0000000clIkAAI

 

 

2nd attempt using the hyperlink button in the editor...

nic_ran
Contributor
Forum|alt.badge.img+16
  • Author
  • Contributor
  • May 29, 2013
I guess I should have tried things out before claiming they wouldn't work!

 

 

The fanout dataset option on the writer did the trick. This FMEPedia article helped:

 

http://fmepedia.safe.com/articles/Error_Unexpected_Behavior/FME-Server-Workspace-Fails-to-Write-Data

 

 

If the attribute to fanout on has just a single value, then only a single file will be written and the feature types will still get their seperate tabs in the resulting Excel spreadsheet.

 


  • May 22, 2023
I guess I should have tried things out before claiming they wouldn't work!

 

 

The fanout dataset option on the writer did the trick. This FMEPedia article helped:

 

http://fmepedia.safe.com/articles/Error_Unexpected_Behavior/FME-Server-Workspace-Fails-to-Write-Data

 

 

If the attribute to fanout on has just a single value, then only a single file will be written and the feature types will still get their seperate tabs in the resulting Excel spreadsheet.

 

Ten years later, I ran into the exact same problem and managed to solve it with Fanout Dataset! :)