I'm taking a guess here that you're using a dynamic writer with the schema source set to "Schema From Schema Feature?"
You need to make sure that you don't have an attribute called "fme_schema_handling"
See here https://community.safe.com/s/article/dynamic-workflows-advanced-example-modifying-the-s
I'm taking a guess here that you're using a dynamic writer with the schema source set to "Schema From Schema Feature?"
You need to make sure that you don't have an attribute called "fme_schema_handling"
See here https://community.safe.com/s/article/dynamic-workflows-advanced-example-modifying-the-s
Thanks @hkingsbury
I do indeed use dynamic output in a FeatureWriter with schema source set to "Schema from Schema Feature".
However, the final tidbit, about why it's necessary to remove 'fme_schema_handling' from the features, which explains what happens, is missing in the picture. @virtualcitymatt explained that in another of my questions, and the article filled in the blanks.
If 'fme_schema_handling' is set to 'schema_only' on the features, which will happen when you merge a schema feature from a FeatureReader onto the data features, the FeatureWriter will remove the first received feature from the stream, and use this for schema definition only.
If 'fme_schema_handling' is missing (or set to a different value??), it will still use the first feature for schema definition, because dynamic output is requested, but leave it in the data stream.
This does explain the behaviour I've encountered.