How to exclude records without using Exclusion activity

[LakshmiPravallika]

Hi Team,

We have a requirement based on a Boolean Flag we are excluding few records and in the Query conditions there are many links after which we query based on the Boolean's Flag Value.

In our current approach, there are 2 query activities with one having the condition  [Schema1/Schema2/@Flag] equal to "Yes" and the other query having the condition  [Schema1/Schema2/@Flag] equal to "No", then we are using an Exclusion activity and taking primary set as    [Schema1/Schema2/@Flag] equal to "Yes" (1st query's Data) and excluding the 2nd query's records.

Example WF for 1 schema

This approach is done for nearly 40 schemas , which is causing issues and we are required to Optimize the Workflow and reduce the number of activities being used.

Could you Please suggest us the approach to use the single query instead of multiple query's and Exclusion activities

Regards,

Pravallika.

[Heku_]

Hello @LakshmiPravallika, as the schema you are querying is the same, you can put in the same query both conditions, but with  [Schema1/Schema2/@Flag] not equal to "No".

Hope this helps.

Regards,

Heku

[LakshmiPravallika]

Hi @Heku_ ,

We already tried this and its not working. We even tried using Except operator also, still no luck.

Regards,

Pravallika.

[Manoj_Kumar_]

@LakshmiPravallika  Try querying to schema2 directly and then change the dimension to schema 1 when you have the expected results.

[LakshmiPravallika]

Hi @Manoj_Kumar_ ,

We tried to query Schema 2 directly by changing the Filtering dimension to schema2 and used the Change dimension activity to change data back to schema1, still its not working.

Regards,

Pravallika.

[AkshayAnand]

Hi Lakshmi

Could you try using the targeting dimension as Schema 1 but filtering dimension as schema 2.

Kindly let me know if you were able to resolve the issue.

Regards

Akshay

[LakshmiPravallika]

Hi @AkshayAnand ,

Yes tried this approach also, and used Change dimension activity as Manoj said, afterwards to change data back to Schema1, still not working.

Regards,

Pravallika.