Skip to main content
Solved

Upgrade to 2016 - bug in user parameters?

  • January 25, 2016
  • 6 replies
  • 17 views
arnold_bijlsma
Enthusiast
Forum|alt.badge.img+15

I upgraded from v2015 to v2016 today, and I have noticed that a user parameter that is derived from another user parameter is not upgraded properly.

In the attached Workspace, I am creating a SiteName parameter based on the input filename. And I also create a SiteNameGDB parameter for the output filename, based on the SiteName parameter. Unfortunately, when opening this workspace - which worked fine in v2015.0 - in v2016, it has replaced the expression $(SiteNameGDB) with the literal string "__SiteNameGDB_"

Is this a bug?

Best answer by mark2atsafe

I think what's happened is that in 2016 we got more strict about what characters are allowed in a Writer. Since those are invalid characters in that format, we automatically replaced them (whereas we didn't before).

The developers are looking into this - but you could also fix this by setting it with the fanout functionality. I made a short movie to demonstrate how: http://screencast.com/t/hMsU0eayj3

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.

6 replies

arnold_bijlsma
Enthusiast
Forum|alt.badge.img+15
  • arnold_bijlsmaEnthusiast
  • Author
  • Enthusiast
  • 126 replies
  • January 25, 2016

See attached screenshot of the workspace in FME 2015.0 and 2016.0

mark2atsafe
Safer
Forum|alt.badge.img+57
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • January 25, 2016

Hi Arnold

I filed this with our developers. The reference is PR#67755. Could you file a case with the support team and pass on that reference number. Then they'll be able to get that sorted for you.

The support URL is safe.com/support

Regards

Mark

Mark Ireland

Product Evangelist

Safe Software Inc.

FME Evangelist to the Rich and Famous!!
mark2atsafe
Safer
Forum|alt.badge.img+57
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • January 25, 2016

I think what's happened is that in 2016 we got more strict about what characters are allowed in a Writer. Since those are invalid characters in that format, we automatically replaced them (whereas we didn't before).

The developers are looking into this - but you could also fix this by setting it with the fanout functionality. I made a short movie to demonstrate how: http://screencast.com/t/hMsU0eayj3

Hi Arnold

I filed this with our developers. The reference is PR#67755. Could you file a case with the support team and pass on that reference number. Then they'll be able to get that sorted for you.

The support URL is safe.com/support

Regards

Mark

Mark Ireland

Product Evangelist

Safe Software Inc.

FME Evangelist to the Rich and Famous!!
mark2atsafe
Safer
Forum|alt.badge.img+57
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • Best Answer
  • January 26, 2016

I think what's happened is that in 2016 we got more strict about what characters are allowed in a Writer. Since those are invalid characters in that format, we automatically replaced them (whereas we didn't before).

The developers are looking into this - but you could also fix this by setting it with the fanout functionality. I made a short movie to demonstrate how: http://screencast.com/t/hMsU0eayj3

FME Evangelist to the Rich and Famous!!
mark2atsafe
Safer
Forum|alt.badge.img+57
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • January 27, 2016

I think what's happened is that in 2016 we got more strict about what characters are allowed in a Writer. Since those are invalid characters in that format, we automatically replaced them (whereas we didn't before).

The developers are looking into this - but you could also fix this by setting it with the fanout functionality. I made a short movie to demonstrate how: http://screencast.com/t/hMsU0eayj3

Reported fixed for FME2016.1

FME Evangelist to the Rich and Famous!!
arnold_bijlsma
Enthusiast
Forum|alt.badge.img+15
  • arnold_bijlsmaEnthusiast
  • Author
  • Enthusiast
  • 126 replies
  • January 28, 2016

I think what's happened is that in 2016 we got more strict about what characters are allowed in a Writer. Since those are invalid characters in that format, we automatically replaced them (whereas we didn't before).

The developers are looking into this - but you could also fix this by setting it with the fanout functionality. I made a short movie to demonstrate how: http://screencast.com/t/hMsU0eayj3

Cheers Mark. I have made the corrections as shown, and good to hear it'll be fixed in the next release.

Community Stats

32,099
Posts
121,892
Replies
39,744
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.