Skip to main content
Question

List Attribute Issue

  • April 27, 2018
  • 6 replies
  • 59 views
A
Forum|alt.badge.img+1

Hi,

I have the following list attributes set up in an AttributeManager which I am passing to an Excel Spreadsheet Writer set up in Dynamic Schema mode.

The first attribute named 'TEST' is outputting correctly in the Excel Spreadsheet with the values from the field named 'LIST_0' (which is not actually a list, just to confuse) populating the column as expected.

In regards to the second attribute, which I have named dynamically from an actual list called 'LIST_NAME_UNIQUE{}', the column name in excel is outputting the correct name as per the list value I specified, but no values are populating the column.

Can anyone see what I'm doing wrong here? I feel like it is a really simple mistake but I just can't work it out...

I am using FME Desktop 2017.1.1.1

Thanks,

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.

6 replies

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • April 27, 2018

Hi @aquamarine, a list attribute can store multiple values as its elements, but a column in a spreadsheet can contain only a single value. I don't think that the values stored in a list can be written into a column, even though the dynamic schema creates a field name corresponding to the list.

If the list contains two or more values, what value should be written into the destination column?

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
A
Forum|alt.badge.img+1
  • aquamarine
  • Author
  • 271 replies
  • April 27, 2018

Hi @aquamarine, a list attribute can store multiple values as its elements, but a column in a spreadsheet can contain only a single value. I don't think that the values stored in a list can be written into a column, even though the dynamic schema creates a field name corresponding to the list.

If the list contains two or more values, what value should be written into the destination column?

Hi @takashi the actual values are in an attribute called 'LIST_1' but they are not actually a list, I just named it that unfortunately. The thing that is confusing is that the column I named 'TEST' does get populated with the values in the attribute called 'LIST_0' but for the column which I named dynamically, this is not happening...

 

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • April 27, 2018

Hi @aquamarine, a list attribute can store multiple values as its elements, but a column in a spreadsheet can contain only a single value. I don't think that the values stored in a list can be written into a column, even though the dynamic schema creates a field name corresponding to the list.

If the list contains two or more values, what value should be written into the destination column?

If you are going to assign the value of "LIST_1" to "LIST_NAME_UNIQUE{1}" and then use it as a destination attribute name, the assignment should be before create the corresponding schema definition - i.e. "attribute{1}.name".

 

 

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • April 27, 2018

Hi @aquamarine, a list attribute can store multiple values as its elements, but a column in a spreadsheet can contain only a single value. I don't think that the values stored in a list can be written into a column, even though the dynamic schema creates a field name corresponding to the list.

If the list contains two or more values, what value should be written into the destination column?

You can see the difference between TEST and LIST_NAME UNIQUE{1} with the Text Editor.

 

TEST
@Value(LIST_NAME_UNIQUE{1})

 

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
A
Forum|alt.badge.img+1
  • aquamarine
  • Author
  • 271 replies
  • April 27, 2018
You can see the difference between TEST and LIST_NAME UNIQUE{1} with the Text Editor.

 

TEST
@Value(LIST_NAME_UNIQUE{1})

 

I have tried swapping the order (see image below), but it hasn't seemed to make any difference.  Have I misinterpreted what you mean?

 

 

Note: I've renamed the attribute 'LIST_X' to 'ATTR_X' to reduce any confusion.

 

 

0684Q00000ArNBxQAN.jpg

 

A
Forum|alt.badge.img+1
  • aquamarine
  • Author
  • 271 replies
  • April 27, 2018
You can see the difference between TEST and LIST_NAME UNIQUE{1} with the Text Editor.

 

TEST
@Value(LIST_NAME_UNIQUE{1})

 

Oh I finally got it:

 

0684Q00000ArN3iQAF.jpg

I had to be careful to ensure the  had a capital 'V' otherwise it didn't work.

 

 

Community Stats

32,087
Posts
121,850
Replies
39,729
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.