Back to Ideas
30
Like
Follow Idea
Simple query boolean expressions: allow checking without true/false
5174Views
5Comments
Implemented
Aggregates & Queries
Development Environment 11.0.109.0

Normal expressions allow booleans to be evaluated without comparison, and the not operator, e.g.:

if(not myBool, "hello", "hi")

In simple query expressions however, we need to explicitly check against True or False, and the not operator is not allowed:

Entity.Attribute = False

I'd consider that bad coding style in a normal expression. Why can't we use "proper" boolean expressions in simple queries?

07 Mar 2014
Copy link to comment

The idea here is to let the developer use only the boolean attribute name when setting a filter on an aggregate with it, instead of the attribute name plus the condition (=true or =false).

Please see the attached pictures as an example.
 



Merged from 'Disable the mandatory condition (=true / =false) when setting a filter on an aggregate with a boolean attribute.' (idea created on 2017-08-10 10:54:37 by Paulo Zacarias), on 2017-08-11 15:15:17 by Justin James
10 Aug 2017
Copy link to comment
Merged this idea with 'Disable the mandatory condition (=true / =false) when setting a filter on an aggregate with a boolean attribute.' (created on 2017-08-10 10:54:37 by Paulo Zacarias)
11 Aug 2017
Copy link to comment
Merged this idea with 'Filter Aggregates with just Boolean Variables' (created on 29 Aug 2018 10:01:21 by Reinaldo André Muralha)
06 Sep 2018
Copy link to comment

I think it would be useful if it was possible to filter aggregates with just boolean variables, with a boolean variable IsActive as an example:

- IsActive = true -> IsActive

- IsActive = false -> Not IsActive



This comment was:
- originally posted on idea 'Filter Aggregates with just Boolean Variables' (created on 29 Aug 2018 by Reinaldo André Muralha)
- merged to idea 'Simple query boolean expressions: allow checking without true/false' on 06 Sep 2018 08:23:06 by Kilian Hekhuis
29 Aug 2018
Copy link to comment
Changed the status to
Implemented
on 26 Sep 2018

Hi Kilian Hekhuis,

Thanks for your feedback.

I'm glad to let you know that this improvement has been release on the first version of OutSystems 11 and all later version (Release Notes)

Keep the feedback coming.


Thanks,

04 Jan 2019
Copy link to comment