A BPA workflow's IFS Projection task, meant to update a field at record creation via a Projection call, fails — inspecting the equivalent call in Postman shows IFS itself calling two entity sets together in a single web-service request, but the Projection task configuration only allows specifying one.

All FAQ questions / Workflows and automation

Answer

This is a confirmed platform limitation, not a configuration mistake — BPA Workflow Projection tasks don't yet have complete support for the kind of nested-collection request pattern (multiple entity sets, function calls, or bound actions combined in one call) that the standard client itself sometimes uses internally. Some progress was made from 22R2 onward specifically for read operations, but full support for nested collections in workflow Projection tasks (including for writes like this) wasn't implemented as of that release — if your workflow genuinely needs this pattern, check whether support has been extended on your current release before assuming your own Projection task configuration is wrong.

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