I'm working on converting a 12dxml file to a GIS format with an attribute table like an Esri FGDB feature class. Eventually the workflow will be used to write new data to an editable hosted feature service via a FME Server tool.
Using the xml reader and feature paths I'm able at access and process the xml elements I require and create the output I need. Rearranging the key:value nature of the xml data is a little fiddly, but I've achieved that using Aggregators, AttributeCreators, AttributeSplitting and lastly an AttributeExposer.
Using the AttributeExposer means that I've had to hardcode in the attribute names into the workflow and I'm wondering what the options are for managing these if additional attributes are added to future xml files?
Perhaps using a published parameter or a txt file that stores a list of attribute names that can be dynamically read into the AttributeExposer?
Exposing the attributes may not even be necessary if I make use of the dynamic options when writing the data out. I plan to look into this next.
