Data flow - filter on repetative element

In the ItemMaster BOD there is a repetetive element for the alternative UOM. The file produced looks like this:

I want to filter items that has an AlternateUOMCode that is PA.

In the filter properties in the Data Flow I have added the element as an attribute:

In the conditions I have checked for value PA:

However, this does not work. I have other filters as well and when I remove this condition it works.
Does it only match against the first element? Is there any other way of achieving the filtering I want?

Find more posts tagged with

ION Connect

Accepted answers

Maxime Richard

Hello,

Kevin is right : filter is done based on attribute value. Standard OAGI attribute "listID" is not used (M3 in my case).

Maybe a XSLT mapping could add artificially such a tag

Data is transformed like this:

This way you could filter BODs and test existence of the tag.

After some tinkering...

All comments

Kevin Heiman

Depending on your BOD structure, a test should apply to any one of the repeating elements.

Review https://docs.infor.com/ion/2022.x/en-us/iondeskceug_cloud_osm/default.html?helpcontent=lsm1436532186757.html

".. condition is met if the application document contains at least one value that meets the condition ..."

If there is an attribute, you can filter elements using the attribute, however in yor example there is no attribute.

Maybe share the full redacted / obfuscated document for reviewing.

Kevin Heiman

In reviewing your topic, I replied in context of Event/ Monitoring. I don't think that concept applies in a Flow Content Based routing )CBR). A suggestion would be to add a atribute to the elements and use an attribute filter.

I will research if there is another option in CBR or others can advise.

Maxime Richard

Hello,

Kevin is right : filter is done based on attribute value. Standard OAGI attribute "listID" is not used (M3 in my case).

Maybe a XSLT mapping could add artificially such a tag

Data is transformed like this:

This way you could filter BODs and test existence of the tag.

After some tinkering...

Daniel Henningsver

Thanks, this works to solve my usecase. I had to use *:AlternateUOMCode in order for it to work. I'm not sure about the difference.

Maxime Richard

It's because of the default namespace xmlns=""">schema.infor.com/.../2" In my example, i removed it for testing purpose.

As xsl:copy copies namespace, you should have an xmlns="" as attribute in the <AlternateUOMCode> tag.

Copyright © 2025 Infor. All rights reserved.