A workflow API task that creates a nested entity record (like a customer order line discount) fails with a conflicting-discount-type error, even though only one discount type (amount or percentage) is actually being set in the call.

All FAQ questions / Workflows and automation

Answer

Check whether a variable from an earlier step in the workflow (like a previously-created DiscountAmount) is being silently inferred into the later Create-operation API task alongside the values you explicitly set — this variable-inference behavior can smuggle in a conflicting value you didn't intend to pass. Either add a script task before the API task that explicitly clears/removes that inferred variable, or use the API task's "Only Explicit Parameters" option to disable automatic variable inference entirely, so only the parameters you've deliberately mapped are actually sent.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Workflows and automation questions