Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Everyone,
I’m not the first to notice this, but I want to understand if it’s impacting anyone else in the community:
Did you know that if you place a constraint on a variable that the constraint actually only applies to the variable when exposed in an input box? If you use a calendar object to set a date variable (for example), the constraint is completely ignored.
QlikView support has deemed that this is functionality as designed. I have raised this as a feature request.
Do you agree that variable constraints should be respected regardless of input method?
Please post comments below.
Thanks!
Hi,
Place an Idea for that. I think it's a good idea and that helps R&D people to check which features are requested, and why.
Miguel
Awesome! I had no idea that ideas even existed. I'll add it there.
I know how to define a constraint on an Input Box, but not a variable.
Where do you define a constraint on a Variable?
Thanks,
Rob
I have always set constraints in document properties, under the variables tab. I've always assumed that I was constraining the variable. I see now that where I was placing them says INPUT Contraints. and these constraints are inhereted by INPUT BOXES, but Calendar objects do not have such input constraints.
Thanks. Can't believe I never noticed that!
-Rob
Hi.
I have 2 variables. vPlazoOperacion01, and vPlazoOperacion02.
vPlazoOperacion01 must be greater than vPlazoOperacion02.
I have tried some clauses but none works.
Do you know the correct syntax?
Thanks.
In the Custom Constraint expression, use "$" to refer to the input value being tested. So your constraint for vPlazoOperacion01 would be
=$ >vPlazoOperacion02
-Rob
Thank you!
I couldn't figure that syntax out. It must be in the manual.
I also see that a constraint is valid for the whole document even when I try to change it in the variable overview.
Christian.