The filter would look like this: ((market == "ABC" || businessUnit == "BU1244") && !(market == "ABC" && businessUnit == "BU1244"))
Scenario#2 is exactly what @j_place filter condition does and the correct representation in terms of filter condition is (market != “ABC” && businessUnit != “BU1244”)
Alternate option: As you are using a web service source, consider filtering the required values directly in the account aggregation API (if your API supports it) instead of relying on source config filters and this will also help improve the aggregation performance.
Hello @Soundary
I would recommend you using this documentation to get this handled, as per the doc the things matching the filter will be skipped from being brought into ISC. IdentityNow Account Filtering during Account Aggregation - Compass .
So, as per the same I would recommend below operations, either of them should work:
Option 1:
(market != “ABC“) || (businessUnit != “BU1244“)
So the subsequent API call payload should look something like this for the value component: “(market != \“ABC\“) || (businessUnit != \“BU1244\“)”
Option 2:
!(market == “ABC“) || !(businessUnit == “BU1244“)
So the subsequent API call payload should look something like this for the value component: “!(market == \“ABC\“) || !(businessUnit == \“BU1244\“)”