When we choose <ask the user> for the filter's argument, it will be good to have an option for mentioning a default value for the choice.
ID 675
Category Setup
Author Arnold Hakobyan
Date Created 9/8/2013 11:19:16 PM
Date Updated 10/10/2013 8:50:12 AM
Status New Idea
Score 110
Promoted By
martin oliver
Philipp Matuschka (MMB)
Rick Cogley
José de Alencar Pereira Neto
Megan Pillsbury
anjuim moied
Arnold Hakobyan
Smith Mountain Services
Michel Gauthier
basenine
Scott Miller
Comments
José de Alencar Pereira Neto 6/21/2012 9:16:50 AM
self-explanatory
Kirill Bondar Staff 6/21/2012 10:28:01 AM
In fact we were quite close to implement this feature - Parameter() syntax was designed to allow default values as well.
But what could be the value? The constant? Unlikely. Calculated value? In the view execution context we have no current record, therefore can not access columns. This left us with two possible values for default - the User() and simple expressions based on Today().
But now with introduction of user properties table we might want to think of it again.
Philipp Matuschka (MMB) 6/25/2012 3:39:47 AM
Sounds good. Also while looking at this area, could we give the user control of whether the query is =, >=, <=, contains, etc etc.
At the very least, could the screen show which of those it is
Philipp Matuschka (MMB) 9/10/2013 12:54:59 PM
It would also be useful if the user was shown which logic is being used (=, Not=, Contains, etc). Even better would be if they could select the logic.
Slava Shinderov Staff 10/10/2013 8:50:12 AM
Merged with: 526 - Default Value as additional option in <ask the user> Matching Filter option
