NOT(EXISTS MemberBlocks WHERE (MemberBlocks.BlockedMember=LoggedInMember AND MemberBlocks.Member=Member))
The above works great in a WHERE clause for a query, but in an "Applicable" condition on a query grid record operation, is ignored.
Member owns MemberBlocks (allow multiple) MemberBlocks.Member points back to the parent Member. MemberBlocks.BlockedMember points to a peer Member (who is being blocked).
So, the condition should not allow the (Email in this case) record operation to appear if the MemberBlocks.BlockedMember is the LoggedInMember, for the Member that has "blocked" them.
I use "Applicable" conditions on query grids record operations, and they work great. this one gives no error but is just ignored.
Dave
Applicable on query grid record operation ignored (SOLVED)
Applicable on query grid record operation ignored (SOLVED)
Last edited by ddumas on Mon Dec 30, 2019 1:31 am, edited 1 time in total.
-
- Posts: 7523
- Joined: Sun Apr 24, 2005 12:36 am
- Contact:
Re: Applicable condition on query grid record operation igno
Not all expressions are supported in applicability conditions. Check out Tomcat log which should have diagnostics on how this condition is evaluated. Most probably it's a limitation.
Aware IM Support Team
Re: Applicable condition on query grid record operation igno
Not a problem. I can add the filter as an additional WHERE clause condition to the underlying filter for the query.
Dave
Dave
Re: Applicable condition on query grid record operation igno
The workaround worked - adding the applicability condition as an additional WHERE condition to the underlying query .
Dave
Dave