Skip to main content
Question

The AttributeExploder transformer seemingly exposes nonexisting list attributes when newly added to the canvas (using the default settings with Exploding Type = 'Features' instead of list)

  • January 15, 2020
  • 1 reply
  • 19 views

thijsknapen
Contributor
Forum|alt.badge.img+11

The AttributeExploder transformer exposes nonexisting list attributes when newly added to the canvas (using the default settings with Exploding Type = 'Features' instead of list)

For this transformer I would guess that the Exploding Type would regulate which features should be exposed at the output port. I.e. using the default names (_attr_list, _attr_name, _attr_value);

Choosing the Exploding Type = 'Features' should only expose the attributes '_attr_name' and '_attr_value', while choosing the Exploding Type = 'List' should only expose the list attributes _attr_list{}._attr_name and _attr_list{}._attr_value.

This is only not the case when the transformer is newly added to the canvas, but is the case when the Exploding Type attribute is altered... Furthermore, I would guess that when the Exploding Type is set to features the Attribute Name/Value Label field should be greyed out, similar to how the List Name field is greyed out when the Exploding Type is set to Features. See also the following;

0_AttributeExploder_newlyAddedToCanvas;

1_AttributeExploder_ChangeExplodingTypeToList;

2_AttributeExploder_ChangeExplodingTypeToListAndBackToFeatures;

Peculiarly when the transformer is newly added to the canvas (item 0), internally the list attributes don't pop up;

However, in workbench they are being picked up;

Can someone maybe explain me what is happening here?

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.

1 reply

rahulsharma
Safer
Forum|alt.badge.img+10
  • Safer
  • 359 replies
  • January 20, 2020

Hi @thijsknapen,

 

Thanks for bringing this issue up, it appears to be a GUI regression, and I have filed an internal issue to get this fixed