Skip to main content
  • EN

 Hi, 

I am having an issue with feature readers and XML. I have a process which downloads an XML file from an ftp site, and the file name changes daily.  Upon download, I am trying to trigger a second process which reads the downloaded xml, so I can then split it into separate records (hence why reading in as text will not work, as I need the xml fragments). I use a path reader, to get the file name, but when I put ‘Path_Windows’ as the dataset, i get this error: 

error message

 

 

If I choose to ignore the message, and run to the featurereader, It reads in the correct amount of records (59), but the schema is blank. 

Blank Schema

 

Log Error message

 

 

 

Now, i know for a fact that my xml does in fact, have a schema, because if I hard code the file name in the feature reader, it works perfectly fine. (see below)

 

 

 

FeatureReader with hard coded file name
Successfully read

 

The parameters are identical on both. 

 

FeatureReader Parameters

 

 

I am at a total loss as to why when I want to put in a dynamic file name, the whole process falls over. If I was just writing the xml out, I would read it in as a txt file as a work around, but because I need to process the xml a certain way, i need those xml fragments in order to get my desired output. 

 

 

I am in no way an xml expert, so any help would be appreciated!

 

 

 

 

FME(R) 2021.2.6.0 (20220727 - Build 21821 - WIN32)

 

 

 

 

 

 

 

 

This is because, if you use a dynamic filename, the schema is unknown. You can use an AttributeExposer to expose the unexposed attributes. You can simply choose import, import from feature cache.

This is because, if you use a dynamic filename, the schema is unknown. You can use an AttributeExposer to expose the unexposed attributes. You can simply choose import, import from feature cache.

 

Thank you so much! I exposed the xml_fragment from the cache, and this has worked perfectly :) 

 

Cheers :)

In my opinion, FME works best with 2 screens. One for the workflow, one for the results. Then the log is not hidden behind the visual preview window and when you select a feature, you can see the unexposed attributes in the Feature Information window.

You can configure this via Tools, FME Options, Data Inspection, Inspect with Data Inspector when Visual Preview window closed.

Reply


Community Stats

30,108
Posts
114,295
Replies
37,744
Members
Terms & ConditionsCookie settings
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.