Array of strings as input in API connection point from Document path

Runar Sivertsen

Hello,

I am trying to use an array of strings as input in an API connection point from a document path.

This is the input I'm using:

However, only the first Item in the array makes it as an input parameter:

Here is the very simple document schema I made to test:

What am I doing wrong here? Isn't the wildcard '*' in '$.products[*]' used to grab all the elements in the array?

Any help is appreciated

Find more posts tagged with

ION Connect

Accepted answers

All comments

Danil Klemeshov

Hello Runar,

It is by design.
In an API connection point when using a path pointing to a repeating element, or is part of a repeating structure, the first item is retrieved by default. To extract a different occurrence, you can use index and filter expressions.

Link to the documentation: docs.infor.com/.../default.html

Runar Sivertsen

Thank you for the quick response

But using filter expressions or index intervals still only gives me the first element in the array, or the first element that equates to true in the filter expression. Is there any way to extract all elements in an array in the Path expression?

The API takes an array of strings with the product number as a parameter, and I need to use all product numbers from the incoming document as the input for this request parameter

Danil Klemeshov

Hello Runar,

Could you describe the use case you have in more detail?
It can help to think about a workaround solution.

Runar Sivertsen

Of course, thank you!

We have an integration updating product information to a PIM system for a client, and most of it works fine. Some messages are triggered on changes on a variety of fields in MITMAS, and a few other tables. The messages triggered from table updates work fine, as they only send a single product message.

However, they also want to have a batch item transfer. this trigger is now set up to use MHS630. The majority of this one also works fine, except for one part of the message, packaging attributes. This requires an identifier from the PIM system to allow us to update, and make sure we update correctly. We are therefore running a GET transaction first to get these packaging identifiers, and then we run a merge function in the data flow with a script to map these identifiers to the correct place. Once we have these identifiers in the message, we can POST to the PIM system.

This works fine with single product messages, as the API connection point uses the first ProductNo it finds, as you can see above. However with a batch transfer and multiple products in the same message, we are unable to use all these product numbers in the request parameter ProductNo.

The document looks different from what i've posted above. I just tried to write a script to extract the product numbers in a single array and then use as input. But this is what the document normally looks like:

Copyright © 2025 Infor. All rights reserved.