Hi,
I have implemented a new Projection action intended for use in an integration scenario, where the action accepts an array as its input parameter. During execution, if an error occurs while processing an individual node within the array, the entire execution halts.
I would like to modify this behavior so that:
-
The execution continues for the remaining nodes despite encountering errors, and
-
The details of any failed nodes are captured and returned to the user.
To achieve this, I reviewed the implementation approach used in Core, specifically how similar logic is handled. Based on that analysis, the general steps seem to be:
-
Defining the action in the corresponding
.projection
or.fragment
file -
Implementing the logic in a Function (rather than a Procedure) to allow returning a result structure that includes both successful and failed nodes
An example I referenced is the InventoryPartInStockList.fragment
, which follows this pattern.



I have followed the same steps in my implementation. However, during code generation, I encountered an issue: the generator does not recognize the function and instead generates a corresponding Procedure, which leads to an error.




Could you please advise on how to ensure the code generator correctly recognizes the action as a Function, or suggest an alternative approach to enable non-blocking processing of array nodes with error reporting?
Product Version: 23R2
Thank you in advance,
Nija