Differences Between Input Message Formats
The following list describes the differences between the input message formats:
The iterateOver attribute for the orchestrationStep element is supported only by the standard JD Edwards EnterpriseOne input message format.
When using the "detail" form action type with the standard format, it will automatically iterate over all detailInputs and repeatingInputs in order to add multiple rows to a grid. If the generic format is used, only a single grid row can be added.
As shown in Example, "detailInputs" would correspond to grid data; "repeatingInputs" would correspond to individual rows that contain "inputs" that correspond to columns.
If you have a power form with two grids, you could populate both grids using two "detailInputs" structures with different "name" values that correspond to the different grids. "repeatingInputs" would contain a list of rows and for each row you would define a list of "inputs".
You could also define a CrossReference orchestration step with
iterateOver="GridData"
that converts the item value into an
EnterpriseOne specific item number. For example, if A123=220 and A124=230, the single
orchestration step would convert both.