AND condition for filter in DataFlow doesn't work

DM9346
DM9346 Member Posts: 8

Hi All,

I have a dataflow wherein I have a filter node however, the AND condition doesn't work. If I use the OR it does work but never the AND condition.

Has anybody experienced this?

Answers

  • Prabodha Amarapema
    Prabodha Amarapema Member, Infor Partner Posts: 34

    No, AND filter should work, make sure your attributes mappings and conditions are correct

  • DM9346
    DM9346 Member Posts: 8

    Mappings and conditions are correct but it still doesn't work. I tested with OR and that one works.

  • Prabodha Amarapema
    Prabodha Amarapema Member, Infor Partner Posts: 34

    Can you share a screenshot of the condition

  • Aaron Roma
    Aaron Roma Member Posts: 4

    Use AND in filters all the time and have never had an issue. As Prabodha mentioned, if you can share a screenshot, we may be able to help out. Just to be sure the basics are covered, you have selected the combined condition in the "Used Condition" field, yes?

  • Kevin Heiman
    Kevin Heiman Member, Staff Posts: 16

    For reference this section covers filters in flows with a fair amount of detail and considerations as well as a "Combined condition" section with examples. Check the data has content, if your are using attributes that you are filtering to the correct attribute.

    You can also see the filter step in OneView and see the comparison used.
    As others have noted, more specifics would help to narrow in on what steps you need to consider.
    Filter Routing has worked well in the scenarios I have created.

  • DM9346
    DM9346 Member Posts: 8

    Here's the XML from that day.

    Here's how I get the attributes. Note that these 2 are now separated since I asked this question as it was not working.

    This is the one that passes when I use OR condition.

    This is the AND condition that doesn't pass

  • Carsten Steinhoefel
    Carsten Steinhoefel Member, Staff Posts: 23

    You have probably already tried this but does the filter pass "Level1Hierarchy EQUALS 'C'"? It looks like it should but that's what has not been tested by the OR condition above.

  • DM9346
    DM9346 Member Posts: 8
    edited November 18

    By extension yes. Right now I changed it to a routing then filter and the C condition routing is working then the filter is with regards to 2800 or 2801.

  • Carsten Steinhoefel
    Carsten Steinhoefel Member, Staff Posts: 23

    I have set up a similar condition and it is working for me. However I could not get the filter to look exactly like yours. I have always got the simple OR branch first independent of the order I defined them in:

    In my case the BOD has ItemType='Purchased' and ItemGroup='P30010'.

    I would test once with the simple Hierarchy = 'C' filter just to make sure it passes. Then I'd delete and re-add the combined conditions and test again.

  • DM9346
    DM9346 Member Posts: 8

    Thank you very much. This is how I did it before(I briefly recreated it). This results in the condition in my comment above.