Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Bucharest on Sept 18th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Input constraints (read only and no constraints) in two input boxes for the same variable

Hi all! I use Section Access in my report.

I have the input box to input variable value.

Some users (as Administrator) can input value for Variable 1 - 'i'.

Some users (as User) can't do it, they can only "read only" the value of i.

I decided to create copy of input box object and than change the proporties for this input boxes:

1) Input box for Admin - "No constraints ":

IB1.png

2) Input box for User - "Read only":

IB2.png

But!! When i change this proporty in any input box, it will change every input box.

I.e. i coulnd't have another prorepties for 1 variable.

This property 'Input constraints' isn't property of object, but property of variable?

Could you help  me with this issue?

How can i resolve it?

P.S. I have 5 input boxes including 45 variables ( "No constraints"  - for admin ) and the same 45 variables ("read only" - for users)

4 Replies
Not applicable
Author

Hi,

input constraints is a property of variable.

Try to create two variables and two inputbox, one for user and one for admin.

Add an attribute field (ex. UserType) with role USER or ADMIN (like a  restriction field)  linked to each user defined in the section access.

So use a conditional layout on the two object like this:

Show Conditional Expression for Admin: (UserType='Admin')

Show Conditional Expression for Admin: (UserType='User')

Hope this helps

MC

Not applicable
Author

Thanks Mario!

i didn't know that it is a property of variable . Thank you

Anonymous
Not applicable
Author

Kseniya,

What if you give access to the input box for ADMIN only?  As for the user - hide the input box and show the same variable in a text box (which is read-only by its nature).

Regards,

Michael

Not applicable
Author

Hi Michael!

This is a good idea! Thanks!