Dynamic and Generic are two aspects of FME functionality, alike in purpose but still distinct features in their own right. To put it succinctly, Dynamic ≠ Generic. So this post explains the differences (and similarities) and covers the huge improvements made for multipurpose workspaces in FME2010.
Oh what a tangled web you weave, when first you practice to use the SchemaMapper. Hopefully this post will unpick some of the more tangled issues when you dive into mapping Feature Types and Attributes with multiple where clauses from the same lookup tables, or when using it to set attribute values like a dynamic ValueMapper transformer.
Mapping FME Feature Types (layers) is greatly complicated when there is no direct correlation between the source and destination schemas. Hundreds of tests and connections can result in a workspace worthy of the “FME Chamber of Horrors”. The SchemaMapper transformer can help by testing the features against mappings defined in a lookup table. Or, as Kenny Rogers might say, “I just dropped a SchemaMapper in, to see what condition my Attr Value Field was in”.
As Spiderman once said, with great power comes great responsibility; and FME’s SchemaMapper transformer certainly has such powers and definitely needs a responsible user. In previous SchemaMapper posts I showed simple Feature Type and attribute mappings. Now it’s time to take your SchemaMapper use to the next level with conditional schema mapping.
The SchemaMapper transformer is - rightly or wrongly - infamous for its complexity. But in a previous SchemaMapper post I showed how simple it was for mapping attributes from one name to another, and now I’ll demonstrate basic techniques for mapping Feature Types.