A workflow Call action needs to invoke a bound action, but the designer gives no way to set the EntitySet the bound action needs — the action call just fails because the entity type parameter can't be supplied. How do I call a bound action from a workflow?

All FAQ questions / Workflows and automation

Answer

Bound actions don't let you pass an entity-type parameter explicitly in the workflow designer, which is why the Call activity doesn't prompt for one. Instead, add an API Read activity that reads the exact record you want to act on first (including any VirtualSet key it needs), then add a Call activity for the bound action with no parameters — the workflow implicitly uses the record from the preceding Read as the action's target. This also applies when the bound action is exposed on a VirtualSet-based entity rather than a normal one.

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