span8
span4
span8
span4
Version 1 of the AttributeExposer (FME 2017.0+) actually works as it should - it merely exposes attributes already on features to FME Workbench.Version 0 (FME 2016 and earlier) actuallyadded(orcreated) the attributes fme_basename and fme_dataset oneveryreader, even if the user exposed a different attribute, e.g.fme_geometry, and the connection to the AttributeExposer was disabled.
The best solution for FME 2017+ is to expose fme_basename and fme_dataset on the readers only if you need them.To learn how to expose any attributes on more than one reader, seehttps://knowledge.safe.com/questions/49944/expose-format-attributes-such-as-fme-basename-for.html
I do not believe in that "The best solution for FME 2017+ is to expose fme_basename and fme_dataset on the readers only if you need them".Adding attribute exposer is a good visual indicator that some other but just user attributes are used in the workspace.Same with adding reprojector instead of/in addition to just setting writer to a different coordinate system than the reader has.Such things improve perception of workspace design.
read user attributes only0 Answers
Undefined macro `VALUE_ATTR_ALIAS'3 Answers
Merge/Aggregate Data within FME3 Answers
WorkBench Execution4 Answers
© 2020 Safe Software Inc |Legal