I have a workflow where I need to use the featureReader to read in some data. The dataset parameter is an attribute containing a wildcard character in the path.
Is there any way of determining the actual file a feature belongs to, as the fme_dataset attribute does not seem to be present on the feature (it's not a matter of exposing it, it's not there to be exposed).
I can't reproduce this with a Text File reader but I think I have seen this before... What is the format? What FME version? Did you merge initiator attributes?
I can't reproduce this with a Text File reader but I think I have seen this before... What is the format? What FME version? Did you merge initiator attributes?
2018.1 (18528). The actual data is xml, but I also tried a few other vector formats. Raster formats do have the fme_dataset present.
Merging initiator attributes gives the initiating feature's fme_dataset, not merging attributes it's not present.
2018.1 (18528). The actual data is xml, but I also tried a few other vector formats. Raster formats do have the fme_dataset present.
Merging initiator attributes gives the initiating feature's fme_dataset, not merging attributes it's not present.
Couldn't reproduce in 2016 (sorry) but can reproduce in 2018.1.1 (18567) with XML reader and path without wildcard. Weird, think it might need a ticket.
Workaround could be to use a FeatureReader Directory and File reader first, then merge initiator attribute, but this is not how it should work I think.
I can get the fme_dataset value with no issue in 18552. You do need to expose as both a schema parameter and in the additional attributes to expose box if using a generic output port
I can get the fme_dataset value with no issue in 18552. You do need to expose as both a schema parameter and in the additional attributes to expose box if using a generic output port
With an xml file? I just tried in build 18552, and it still comes up as missing, even when using a hardcoded path and feature type.
With an xml file? I just tried in build 18552, and it still comes up as missing, even when using a hardcoded path and feature type.
Yes, just updated with a screenshot of the output above
Yes, just updated with a screenshot of the output above
That's special. I wouldn't have thought to expose the schema attribute in the parameters, especially since the feature reader is set to Data Features.
That's special. I wouldn't have thought to expose the schema attribute in the parameters, especially since the feature reader is set to Data Features.
I ran into the same problem before. I think it might be inconsistent between file types but I didn't think too much about whether it was the 'correct' behaviour as long as i had something working.