Skip to main content
Question

FME Server published parameter file naming

  • May 7, 2019
  • 4 replies
  • 61 views
J
Forum|alt.badge.img

I have a workspace with a published parameter setup to receive a name from the user that is then appended to the file name in an Excel writer. It works just fine in FME desktop, but when the workspace is published on FME Server it doesn't.

In the writer destination file I have ./Filename_$(value).xlsx

If I set the value parameter to "apples" FME Desktop generates a file named Filename_apples.xlsx

FME Server creates a file named Filename_$(value).xlsx

Do I need to use escape characters or something to force FME Server to use my parameter?

FYI I'm using FME Server 2018.0 and publishing using the same version of FME Desktop.

Not a critical issue, but I'm curious why it's not working.

Thanks

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.

4 replies

nielsgerrits
VIP
Forum|alt.badge.img+64

This works for me in Server 2016. I use this often, but I usually don't write to Excel. But it works with dwg / gdb.

But all my paths are hardcoded UNC, not relative. And I think my dynamic filenames are set in attributes, based on parameters.

Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
J
Forum|alt.badge.img
  • jamess
  • Author
  • May 8, 2019

This works for me in Server 2016. I use this often, but I usually don't write to Excel. But it works with dwg / gdb.

But all my paths are hardcoded UNC, not relative. And I think my dynamic filenames are set in attributes, based on parameters.

Thanks for the suggestion. I have tried the Fanout Dataset option within the writer using an attribute for the file name that is generated from the published parameter within the workspace. This appears to be the only way to use an attribute value as the file name within the Excel writer.

The good news is it works. It just creates the files within separate directories, which I can live with.

However, the way I had it setup originally really should just work in Server as it does with Desktop. If anyone knows why it doesn't I'd be interested in hearing about it.

nielsgerrits
VIP
Forum|alt.badge.img+64

Thanks for the suggestion. I have tried the Fanout Dataset option within the writer using an attribute for the file name that is generated from the published parameter within the workspace. This appears to be the only way to use an attribute value as the file name within the Excel writer.

The good news is it works. It just creates the files within separate directories, which I can live with.

However, the way I had it setup originally really should just work in Server as it does with Desktop. If anyone knows why it doesn't I'd be interested in hearing about it.

Just tested this in 2016 and it works as it should:

Make sure there are no quotes around it.

Our server is on Windows. I tried both ./Filename_$(value).xlsx and .\\Filename_$(value).xlsx which made no difference. Maybe it does on your installation if it is not on Windows?

Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...
J
Forum|alt.badge.img
  • jamess
  • Author
  • May 8, 2019

Just tested this in 2016 and it works as it should:

Make sure there are no quotes around it.

Our server is on Windows. I tried both ./Filename_$(value).xlsx and .\\Filename_$(value).xlsx which made no difference. Maybe it does on your installation if it is not on Windows?

Thanks again for the assistance. In FME 2018 the Feature Writer Parameters for Excel look much different...

XLSX Writer options...

Unless there's another way to access and change the Feature Writer Parameters I just can't find the same options that you have shown. Perhaps at 2018 there were significant changes to the Excel writer? Potentially breaking the functionality we are testing.

I think I'll log a help request to get to the bottom of it... and report back with the findings.

 

Community Stats

32,181
Posts
122,172
Replies
39,855
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.