Skip to main content
Solved

BulkAttributeRenamer bug with non-ascii attribute names

  • August 6, 2019
  • 8 replies
  • 43 views
S

Just upgraded to 2019.0.2.0 and the BulkAttributeRenamer shows some unexpected behaviour, when an attribute's name contains special characters (in my case German umlauts "äöü", but I assume any non-ascii trigger the problem). Problem did NOT occur in 2017.1.2.

The transformer's mode of operation (prefix, regex etc.) doesn't seem to matter: simply adding a prefix is enough to trigger the bug.

Minimal example to reproduce:

  1. Create a feature with an attribute name, e.g. "ÄTTRIBUTE" = 1
  2. Add a prefix to it with BulkAttributeRenamer, e.g. "FOO_"
  3. Note you now have "FOO_ÄTTRIBUTE" as expected, but with an empty value (instead of =1) AND you still have "ÄTTRIBUTE" carrying the original value (only visible when inspecting all of the feature's attributes, i.e. click the row in inspector)

Can anyone else reproduce this?

Best answer by fmelizard

Hi @takashi and @schauri, I've verified that the BulkAttributeRenamer worked in FME 2018 but not in FME 2019. Problem now reported as FMEENGINE-61150

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.

8 replies

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • August 6, 2019

Hi @schauri, yes I can reproduce the issue with Japanese characters. It's definitely a bug in FME 2019, and has not been resolved yet in the latest release version 2019.1.

I found the issue in FME 2019.0, but forgot if I have reported this to Safe support.

Please check this @danatsafe

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
fmelizard
Safer
Forum|alt.badge.img+20
  • fmelizardSafer
  • Safer
  • 3719 replies
  • Best Answer
  • August 14, 2019

Hi @takashi and @schauri, I've verified that the BulkAttributeRenamer worked in FME 2018 but not in FME 2019. Problem now reported as FMEENGINE-61150

fmelizard
Safer
Forum|alt.badge.img+20
  • fmelizardSafer
  • Safer
  • 3719 replies
  • August 14, 2019

Hi @schauri, yes I can reproduce the issue with Japanese characters. It's definitely a bug in FME 2019, and has not been resolved yet in the latest release version 2019.1.

I found the issue in FME 2019.0, but forgot if I have reported this to Safe support.

Please check this @danatsafe

Hi @takashi and @schauri, I've verified that the BulkAttributeRenamer worked in FME 2018 but not in FME 2019. Problem now reported as FMEENGINE-61150

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • August 14, 2019

Hi @takashi and @schauri, I've verified that the BulkAttributeRenamer worked in FME 2018 but not in FME 2019. Problem now reported as FMEENGINE-61150

Hi @danatsafe, thanks for filing the problem.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
H
Forum|alt.badge.img+2
  • hollyatsafe
  • 719 replies
  • September 3, 2019

Hi @takashi and @schauri,

A recent update to FME has resolved the issue with the BulkAttributeRenamer not correctly handling attributes containing special characters.

You will find the update in our latest FME 2019.2 beta b19752 available to download from safe.com/beta.

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • September 4, 2019

Hi @takashi and @schauri,

A recent update to FME has resolved the issue with the BulkAttributeRenamer not correctly handling attributes containing special characters.

You will find the update in our latest FME 2019.2 beta b19752 available to download from safe.com/beta.

Thanks for the fix and your notification!

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
S
  • schauri
  • Author
  • 1 reply
  • September 4, 2019

Hi @takashi and @schauri,

A recent update to FME has resolved the issue with the BulkAttributeRenamer not correctly handling attributes containing special characters.

You will find the update in our latest FME 2019.2 beta b19752 available to download from safe.com/beta.

Thanks! Can't test the betas, but I'll trust it will be fixed once we the next stable!

lde
Contributor
Forum|alt.badge.img+5
  • ldeContributor
  • Contributor
  • 4 replies
  • January 14, 2020

Hi all,

Just to share I also add this issue, where some (but not all) values of an attribut are emptied after being processed by the BulkAttributeRenamer (using FME Desktop 2019.1 .0.0 Build 19608). Here is my use case : bugbulkattributerenamer.fmwt

In this workspace I'm trying to prefix all attributes with "__correction__", the issue occures with the attribute called "LocalitéFR". Since upgrading to a new FME version is not an option at the moment, I had to solves this with a PythonCaller (which is not ideal since I have to re-expose all my attributes) ...

Community Stats

32,079
Posts
121,805
Replies
39,710
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.