Timeline for How to transpose a list attribute in FME?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2023 at 11:21 | comment | added | saQuist | Thank you for the follow-up. Using the schema upon export sounds like the way to go. Coming from programming languages like Python and R, these hidden and exposed attributes are just not that intuitive. | |
| Feb 17, 2023 at 18:49 | comment | added | Mark Ireland | Sorry, I don't think it's possible for me to do. I can't add an AttributeExposer to the custom transformer because I don't know what the attributes will be called, and it doesn't work if I try to set it programmatically (because FME doesn't know what they will be called). But if you write the data and the attributes are defined in your schema, then the data would get written without needing to be exposed. | |
| Feb 7, 2023 at 10:42 | vote | accept | saQuist | ||
| Feb 6, 2023 at 11:09 | comment | added | saQuist |
Hi Mark, thanks for the solution, the ListBreaker looks great, however, I noticed that the attributes are not exposed by the ListBreaker. So if I inspect it, there are only the attributes name and platforms with empty values. When I use the AttributeExposer, I can expose the new columns manually (which requies knowing upfront all the names of the attributes). Is there a way to expose them automatically?
|
|
| Feb 3, 2023 at 22:39 | history | answered | Mark Ireland | CC BY-SA 4.0 |