Skip to main content
Solved

FME Hub Transformer Issues


cwarren
Forum|alt.badge.img

I recently just upgraded to the newest beta version and noticed that some of my FME Hub transformers were stated as "incomplete". I looked at the parameters and couldn't tell why it wasn't working anymore. I then rolled back to the latest release version and had the same issues as well. Is there an easy way to trouble shoot why some functionality would break? I just ended up rolling back to a previous version that works correctly for the time being.

The transformers that are giving me issues are the RegexAttributeSplitter and AttributeConcatenator.

Best answer by fmelizard

Hi @madwarren Thanks for reporting this issue to us here at Safe and thanks @takashi for raising this. I can confirm that this is bug is now fixed. You should find the fix included in the latest version of FME 2017 - You can find it here: https://www.safe.com/support/support-resources/fme-downloads/ Please let us know if you find that it is not. Thanks again!

View original
Did this help you find an answer to your question?

5 replies

erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • April 7, 2017

You should report this to Support@Safe.com

Transformers on the Hub should not break with a newer version of FME!


cwarren
Forum|alt.badge.img
  • Author
  • April 7, 2017
erik_jan wrote:

You should report this to Support@Safe.com

Transformers on the Hub should not break with a newer version of FME!

Will do. Thank you!

 

 


takashi
Contributor
Forum|alt.badge.img+19
  • Contributor
  • April 7, 2017

Hi @madwarren, I also noticed that the issue has occurred with the latest FME 2017.0.0.2 build 17280.

Some transformers I developed before - such as RegxAttributeSplitter, AttributeConcatenator etc. allow you to specify the name of a new attribute which will be created by the transformer internally. The functionality has been realized with the BulkAttributeRenamer or ListRenamer (old version).

The mechanism works fine in FME 2017.0.0.1 and earlier, but it has broken suddenly in 2017.0.0.2 build 17280. I've already asked Safe support to investigate what's going on. Hopefully the issue could be fixed in the near future.

Please contact Safe so that the issue could be resolved as soon as possible.


cwarren
Forum|alt.badge.img
  • Author
  • April 7, 2017
takashi wrote:

Hi @madwarren, I also noticed that the issue has occurred with the latest FME 2017.0.0.2 build 17280.

Some transformers I developed before - such as RegxAttributeSplitter, AttributeConcatenator etc. allow you to specify the name of a new attribute which will be created by the transformer internally. The functionality has been realized with the BulkAttributeRenamer or ListRenamer (old version).

The mechanism works fine in FME 2017.0.0.1 and earlier, but it has broken suddenly in 2017.0.0.2 build 17280. I've already asked Safe support to investigate what's going on. Hopefully the issue could be fixed in the near future.

Please contact Safe so that the issue could be resolved as soon as possible.

Thank you Takashi!

 

 


fmelizard
Contributor
Forum|alt.badge.img+17
  • Contributor
  • Best Answer
  • May 5, 2017

Hi @madwarren Thanks for reporting this issue to us here at Safe and thanks @takashi for raising this. I can confirm that this is bug is now fixed. You should find the fix included in the latest version of FME 2017 - You can find it here: https://www.safe.com/support/support-resources/fme-downloads/ Please let us know if you find that it is not. Thanks again!


Reply


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