Skip to main content
Released

List builder option for exposed attributes only

Related products:FME Form
  • December 17, 2015
  • 9 replies
  • 62 views
jdh
Contributor
Forum|alt.badge.img+40

Many times when using the ListBuilder I am only interested in seeing the exposed attributes in the list.

A feature read from text_line reader (text_line_data only visible attribute) for instance produces a list that contains

_list{}.text_line_data _list{}.fme_basename _list{}.fme_dataset _list{}.fme_feature_type _list{}.multi_reader_keyword _list{}.text_line_eol _list{}.text_line_length _list{}.text_line_number _list{}.text_line_type

And only the first is visible on the transformer, all the rest have to be explicitly exposed before they can be removed.

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.

9 replies

fmelizard
Safer
Forum|alt.badge.img+22
  • fmelizardSafer
  • Safer
  • December 18, 2015

How 'bout this. I have long advocated, primarily for efficiency reasons, that we should ask users to specify explicitly what attributes they want added to each and every list. So in the case of ListBuilder, you'd have an additional parameter holding the names of the attrs that you picked to be in the list. I'd want this rolled out to all the transformers that make lists.

What do folks think of that. I suspect it would greatly improve efficiency and reduce memory overhead since right now we are sloshing around a great many attributes in these lists we make which no one ever cares about...

david_r
Celebrity
  • david_rCelebrity
  • December 18, 2015

I think the easiest workaround today would be to insert an AttributeKeeper just before the ListBuilder, then explicitely select those you need.

david_r
Celebrity
  • david_rCelebrity
  • December 18, 2015

That's a pretty neat idea!

jdh
Contributor
Forum|alt.badge.img+40
  • jdhContributor
  • Author
  • Contributor
  • December 18, 2015

AttributeKeeper will not remove fme attributes even if they are not selected.

jdh
Contributor
Forum|alt.badge.img+40
  • jdhContributor
  • Author
  • Contributor
  • December 18, 2015

That would work for me. It would also solve my other pet peeve, having the attributes in the group by on the list. If I'm grouping by an attribute then every single item in the list will have that same value for the attribute and I don't need to store it hundreds of times.

fmelizard
Safer
Forum|alt.badge.img+22
  • fmelizardSafer
  • Safer
  • December 19, 2015

Very very good point. I've got support here and resources lined up. We'll make a run at this for 2016.1

fmelizard
Safer
Forum|alt.badge.img+22
  • fmelizardSafer
  • Safer
  • August 6, 2016

This didn't make it for FME 2016.x, but it is about to appear in the FME 2017 betas. Every place where you are making a list you have the option to specify what attributes you want in the list. You can opt to work as before, where everything is put in, but by default, you need to specify which ones. We think this will be a good result for many scenarios.

jdh
Contributor
Forum|alt.badge.img+40
  • jdhContributor
  • Author
  • Contributor
  • August 25, 2016
from what build is this availble?

 

 

F
Forum|alt.badge.img+1

This has been released as part of FME 2017.0 . Visit http://www.safe.com/downloads to download it and give it a spin.

Community Stats

32,749
Posts
124,193
Replies
41,251
Members
Terms & ConditionsAccessibility 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.