Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
 
					
				
		
Hi
I have an input box which I use for a password to unlock columns on a table.
This works by the keyed data is set as a variable, and the variable is used to show as conditional in the table.
Is there any way I can hide the text in the input box once the variable has been keyed so that the password does not show on the page?
e.g. I key the password into the input box, the variable is then set, and then the input box clears without clearing the variable?
n.b. Section access is not possible in my dashboard.
Any suggestions on how to do this, or other ways around this?
Phil
 
					
				
		
 thomaslg_wq
		
			thomaslg_wq
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		Well, you may already know the only users that should have access ==> and then use this conditional show sentence on your table :
osuser()=DOMAIN\YourUser or osuser()=DOMAIN\AnotherUserWithAccess
 
					
				
		
Hi
I quite like this idea, and it tested well but might be a bit difficult to admin.
Does this work with AD? If so how do you do it?
Regards
Phil
 
					
				
		
 thomaslg_wq
		
			thomaslg_wq
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		No it does not work with AD... OSUser with Active Directory Groups
You may reconsider section access.
BR,
Thomas
 daveamz
		
			daveamz
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		Hi Phil,
Why is difficult to admin?
You can build a matrix with the user domain name and the report or sheet, something like:
UserAccess:
LOAD * INLINE [
ADUser, Report1, Report2
domain\user1, 0, 1
domain\user2, 1, 0
];
Can be loaded from Excel as well.
ADUser field should be unique
And then you can use in the conditional show of any report, sheet, expression etc. the following expression:
=FieldValue('Report1', FieldIndex('ADUser', OSUser()))
Regards,
David
 
					
				
		
 adamdavi3s
		
			adamdavi3s
		
		
		
		
		
		
		
		
	
			
		
		
			
					
		can't you just query AD and use that to map it?
I wrote a blog on returning the users in an AD group to do this sort of thing:
http://qlikanddirty.com/2016/08/25/querying-ldap-to-pull-back-people-in-ad-groups/
