Answered

How do I troubleshoot buttons that are not visible when they are supposed to be in a production app?

(1) Share

Report

Posted on by futr_vision

831 Moderator

I have an app where the home screen has several buttons. They are visible based on the user's access level (user, editor, admin). I've tested with my admin account and I can get all the buttons to appear. I've also changed the admin accounts access level to 'user' and only the user level buttons appear. That's all fine. Where I run into issues is with my test account. The permissions are set to 'user' and no buttons appear. If I change to 'admin' and still no buttons appear. I am thinking it might have to do with permissions on the role level but not really sure what permissions are needed if any.

This is the code I am using to check the user's access level

LookUp('App Users', 'Email Address' = User().Email And ('Admin Access' = "Yes" Or 'User' = "Yes"),true)

NOTE: I also put the users full name and email address on the screen with this code and this all works fine.

User().FullName

User().Email

As an additional test to see if the app is actually reading the table for this 'test' account I added a text box and used this code. It does not return the user's email address as expected.

LookUp('App Users', 'Email Address' = User().Email, 'Email Address')

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

futr_vision 831 Moderator on at

Like (1)

Report

I decided to fiddle with security roles. I changed the Read access from User to Organization and that appears to work. Why is that? Should all my shared tables be set to Organization?

Was this reply helpful? Yes No
v-xiaochen-msft on at

Like (1)

Report

Hi @futr_vision ,

It looks like you created a table that saved each user and their role.

The problem is that many records in the table are not created by the user. So when the user who doesn't have enough security role get records, he cannot find the corresponding records.

I recommend that you set the owner of the user's record to themselves. This way, even if they only have 'user' permission, they can still see their own records.

Best Regards,

Wearsky

Was this reply helpful? Yes No
futr_vision 831 Moderator on at

Like (1)

Report

Thanks. I'm not completely sure I want to go through that process since I need to essentially give them access to almost all other tables since those tables drive the values in the combo boxes in the app. I am finding that the Organization permission seems to fix the issue for and of the create, read, write, etc... permissions needed.

Was this reply helpful? Yes No