Skip to main content
Solved

Upgrade to 2016 - bug in user parameters?

arnold_bijlsma
Enthusiast
Forum|alt.badge.img+14

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

View original
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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+14
  • arnold_bijlsmaEnthusiast
  • Author
  • Enthusiast
  • January 25, 2016

See attached screenshot of the workspace in FME 2015.0 and 2016.0

mark2atsafe
Safer
Forum|alt.badge.img+43
  • mark2atsafeSafer
  • Safer
  • 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.

mark2atsafe
Safer
Forum|alt.badge.img+43
  • mark2atsafeSafer
  • Safer
  • January 25, 2016
mark2atsafe wrote:

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.

mark2atsafe
Safer
Forum|alt.badge.img+43
  • mark2atsafeSafer
  • Safer
  • 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

mark2atsafe
Safer
Forum|alt.badge.img+43
  • mark2atsafeSafer
  • Safer
  • January 27, 2016
mark2atsafe wrote:

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

arnold_bijlsma
Enthusiast
Forum|alt.badge.img+14
  • arnold_bijlsmaEnthusiast
  • Author
  • Enthusiast
  • January 28, 2016
mark2atsafe wrote:

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.

Helpful Members This Week

Community Stats

30,910
Posts
117,115
Replies
38,713
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

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