Changing the port order on your FeatureJoiner can have a potentially negative result. Which option is the correct statement?

Changing the port order on your FeatureJoiner can have a potentially negative result. Which option is the correct statement?

• A. Experienced FME users will expect ports to be in a particular location.
• B. None of the above.
• C. The Crime feature type has to be below the PostalAddress feature type on the canvas.
• D. It will cause an error.

Answer: (B)

In a FeatureJoiner, the order of the input ports on the transformer isn’t what determines how the join works. The join is defined by the join keys and the attribute mapping you configure, not by where the streams are visually placed on the canvas. So changing which input stream feeds which port doesn’t inherently cause a problem or force a specific canvas layout. The only thing to watch for is ensuring you map the correct attributes from the intended side into the output and be mindful of which side’s data you expect to appear where downstream. Because of that, none of the listed statements are inherently true: there’s no universal expectation about a port location, no rule that one feature type must sit below another, and no automatic error just from reordering ports. The real takeaway is that port order can be changed without inherently negative consequences, as long as the join configuration and downstream mappings are correctly maintained.

In a FeatureJoiner, the order of the input ports on the transformer isn’t what determines how the join works. The join is defined by the join keys and the attribute mapping you configure, not by where the streams are visually placed on the canvas. So changing which input stream feeds which port doesn’t inherently cause a problem or force a specific canvas layout. The only thing to watch for is ensuring you map the correct attributes from the intended side into the output and be mindful of which side’s data you expect to appear where downstream.

Because of that, none of the listed statements are inherently true: there’s no universal expectation about a port location, no rule that one feature type must sit below another, and no automatic error just from reordering ports. The real takeaway is that port order can be changed without inherently negative consequences, as long as the join configuration and downstream mappings are correctly maintained.