ION Workflow – How to loop through rows from an M3 “Lst” MI API?

Hi,

In ION Workflow I can call M3 MI APIs that return lists (e.g. OIS100MI/LstLine). The response contains multiple rows/records, but I don’t know how to loop through each row inside the workflow.

Is there a way to do a for-each / iteration over the list in ION Workflow? If not, what is the recommended approach?

In the output parameter mapping I’m using $.MIRecord[0].NameValue[?(@.Name=='PONR')].Value or $.MIRecord[*].NameValue[?(@.Name=='PONR')].Value

But I always get only the first record.

Thanks!

Find more posts tagged with

API

Workflow

ION

Accepted answers

All comments

DM9346

Use the loopback node. The second to the last node besides subprocess. Change from MiRecord[0] to MiRecord[loopcount], define any variable(in ex. loopcount) that you can increment at the end of the loop then use the same variable in the loop condition.

Also, retrieve the number of records variable from the M3 variable results.

Lidia

Thanks! I tried using Loopback with a counter, but the output parameter mapping parser does not accept a variable index.

Example JSONPath: $.MIRecord[CurrentRecord].NameValue[?(@.Name=='PONR')].Value fails with: “Could not parse token… Expected ?, ', 0-9, *”.

It seems Workflow only allows numeric indices (e.g. [0]) or [*], not [variable].
Any workaround to index arrays dynamically in Workflow mappings?

DM9346

Sorry, just looked at my old example and doing it in the workflow requires a lot of manipulation. What I initially said was wrong as you're right. Variables cannot be used on the MIRecord. I had to get the full results and parse them using a script.

A better way to solve it is by doing it in the API Flow with the JQ transform and the loop iteration. I will send you a message.

Lidia

Hi! In case this helps anyone, @DM9346 recommended using an API Flow to be able to iterate over an API of type “Lst…”. In my case it was a CMS100MI API, and it worked.

Here are the steps I followed:

First, I created an API Flow that takes the order number (ORNO) as an input parameter. It calls a CMS100MI transaction to retrieve all order lines (GetOrderLines). In the next step, I get the number of lines returned by the list, and then using a DoWhile loop I iterate through each order line to call an API transaction that updates the free user-defined fields for that line.

Since this API Flow is available in the Infor Gateway, I can call it from my workflow. I’m using a workflow because I needed to subscribe it to an event.

Thank you so much @DM9346 !

Copyright © 2025 Infor. All rights reserved.