Question

1
Replies
1931
Views
 Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN
Avinash.Haridasu Member since 2014 293 posts
Morgan Stanley
Posted: July 13, 2016
Last activity: July 13, 2016
Posted: 13 Jul 2016 3:44 EDT
Last activity: 13 Jul 2016 4:33 EDT
Closed

Report definition does not accept NOT in fliter criteria

I have an optimized property which is used in filter condition of RD.

My requirement is to pull all the records with some not equals condition. For example i need all records which does not contain property id as 1, 2, 3 etc..

When i use "Is not equal" in the relationship i get a guardrail warning as below:

"Filter conditions with relationship operators other than Is Equal may result in poor performance since database indexes will not be used to optimize the query."

I have tried using some NOT in filter conditions to apply but RD does not seem to accept anything other than AND and OR.

Need your thoughts on the not condition in rd or any other alternative for this requiremnt is welcome.

Thanks

Avinash

Data Integration Reporting
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 5 years ago
Posted: 13 Jul 2016 4:33 EDT
Rajiv Nistala (nistr)
PEGA
Senior Manager - Engineering
Pegasystems
IN

The guardrail warning is correct as this might affect performance.


1) Would it be possible for you to justify the warning?


2) Would be possible to get the set of values that should match instead of those that should not match?