Skip to main content
  • EN
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
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...
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
https://safe.secure.force.com/AnswersQuestionDetail?id=906a0000000clIkAAI

 

 

2nd attempt using the hyperlink button in the editor...
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.

 

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! 🙂

Reply


Community Stats

30,162
Posts
114,483
Replies
37,809
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.