+4Is it possible to expose fme_basename on schema features, when reading in just a schema using a FeatureReader? I've tried exposing it on the reader parameters for an excel file, but it does not come through. Adding an AttributeExposer reports it as missing.
Thanks
Best answer by david_r
The schema features do not have an attribute fme_basename. The only available attributes are the following:
The schema features do not have an attribute fme_basename. The only available attributes are the following:
+4The schema features do not have an attribute fme_basename. The only available attributes are the following:
Here's a tip I use often: I you're not sure if a certain attribute is exposable, send the output to the Logger and see what is printed in the log. If you see an attribute in the log that isn't visible in the workspace, then you can expose it to access it.
An alternative is to set a breakpoint in your workspace, and look at the Feature Inspector for a list of all the attributes that are available at that point, exposed or not.
Why is this the case? I want to read schemafeatures from a zipped file containing multiple files (to check for empty layers per dwg zipped in a delivery). Normally I would for instance read a file structure with a Pathreader and then merge the initiator and the schemafeatures (result) together in the FeatureReader that is going to read the actual dwg-file, but since I'm reading from a zipfile (on fme-server btw), the attribute path_windows just shows the name of the zipfile. Having fme_basename or fme_dataset being 'exposable' from the Schema port would be very helpful. Thanks!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
