What happens if this workspace runs on a CSV that does not contain the attribute Close?

What happens if this workspace runs on a CSV that does not contain the attribute Close?

• A. The workspace will run successfully, but the value for the attribute Hours will be incorrect.
• B. The workspace will run successfully with the same output as the current exercise.
• C. The workspace will fail with an error in the AttributeManager.
• D. The workspace will fail with an error in the writer.

Answer: (A)

If an attribute that a calculation relies on is missing, the calculation cannot produce the intended result, but the workflow itself typically continues. In this case, the value Close is used to derive Hours. Without Close, the expression that computes Hours cannot produce the correct value, so Hours ends up incorrect. FME treats missing input attributes as non-fatal; it won’t automatically fail the transfer, it just yields a result that doesn’t match the intended calculation. The workspace runs through to the end, but theHours field is not what you expect. That’s why this outcome happens: the process completes, but the derived value is off because the necessary input attribute isn’t present.

If an attribute that a calculation relies on is missing, the calculation cannot produce the intended result, but the workflow itself typically continues. In this case, the value Close is used to derive Hours. Without Close, the expression that computes Hours cannot produce the correct value, so Hours ends up incorrect. FME treats missing input attributes as non-fatal; it won’t automatically fail the transfer, it just yields a result that doesn’t match the intended calculation. The workspace runs through to the end, but theHours field is not what you expect. That’s why this outcome happens: the process completes, but the derived value is off because the necessary input attribute isn’t present.