When using the SQLITE3 Reader, unchecked attributes from the User Attributes tab are not exposed downstream to any transformer like AttributeManager, -Remover, -Keeper. This behavior is as expected.
However when using the FeatureType downstream on the Requestor side of a FetureMerger and the conflict resolution is set to ‘Use Requestor’ , the unchecked attribute is still active behind the scene and take precedence over the attribute of the same name coming from the Supplier.
It turned out that I need to keep the unwanted attribute ‘checked’ and remove it actively with an AttributeRemover to avoid the unexpected usage in the FeatureMerger.
I also tried to force it by changing the workspace option Reader/Writer Options > Allow Reader Feature Type Editing, but it made no difference.
Question: is this a bug or dangerously intended?
Setup: FME Forms 2023.2 for win 64