Not All Member can See Their Data

[Anonymous]

I have a main landing page. The page header defaults the name of the User from the active directory. A Gallery populates the User's location data based on the name in the User Name of the header.

I have a hierarchy established - National, Region, Location, Employee.

I am going through initial testing. At this point everyone can get in an see their data except those with hierarchy 'Employee'. Staff with approval who are above the 'Employee' in hierarchy can see the employee's data. The member's supervisor (Park), the Region staff (Region) and National staff (National) can see everyone just fine.

Only those members with hierarchy 'Employee' cannot see THEIR OWN data when they log in. What could be causing this issue? These members get a default screen that says they don't have any certifications or qualifications in the system and doesn't let them proceed any further. Why would the system not be seeing the data for the employee but everyone else can?

The default cover image, for when the member actually does not have any certs or quals in the system, has  the following. The below works for all other members except those with hierarchy 'Employee'. No one else is having this issue. All other members are able to see the members they should see, including seeing the data that is not appearing for the 'Employee'.

All data is in the system. Even I can pull them and all the certs and quals up as individuals right now. However, if the member signs in they cannot see their own data and they get the image below. 

Visible = !varIsRoster

varIsRoster = Set(varIsRoster,If(User().FullName in MemberCollection.UsrNm,true));

This is the default screen that appears if system determines the User has no data. It currently is appearing for individuals we know for a fact have data; we can pull their data up as their supervisors and see it in Power Apps. However, they cannot see their own.

[ChrisPiasecki]

Hi @Anonymous,

Can you provide a bit more detail about the the data source you are trying to get data from? You also mention there is a hierarchy in your company, are you referring to Dataverse and hierarchy security there? Or is it just the manager hierarchy within Active Directory?

[JR-BejeweledOne]

Visible = !varIsRoster

varIsRoster = Set(varIsRoster,If(User().FullName in MemberCollection.UsrNm,true));

Try this first.

Drop a button on your canvas and set it's formula to:

 If(
 User().FullName in MemberCollection.UsrNm, Set(varlsRoster, true)

)

Then drop a label on the screen to see the value of varlsRoster

One thing to consider here, the information returned by User() does not always match what is in Office365 or other systems.

You might want to consider using the Office365User connector and Office365Users.MyProfileV2 for this.  There is a difference though in that User().FullName is usually FirstName LastName where as Office365Users.MyProfileV2.displayName is whatever is in Ad, which for most companies is lastname, firstname.

[Anonymous]

It doesn't like that....

It also didn't like it as Office365Users.MyProfileV2.displayName

[JR-BejeweledOne]

Office365Users.MyProfileV2().displayName

[Anonymous]

The data source is an SP list/collection.

The 'Program Hierarchy' is a column in the SP MemberList/Collection. The levels of hierarchy are 'National', 'Region', 'Park' and 'Employee'. 

I have only had this 'roster member' issue with those who are hierarchy 'Employee'; twice this has occurred. All other hierarchy levels do not run into this issue.

The Visible property on the Image associated with this issue is set to !varIsRoster.  

I created a button with this in it, and two labels; one with varIsRoster and the other with varProgramHierarchy. The results are below; they reflect my test account.

I have confirmed that both members are in the system, and we as managers can pull up their accounts and data; however, they cannot access the system beyond the main page where they get the image saying that don't have any certs or quals in the system.

I am in agreements the evidence points to the UserName that auto-populates at load. Though I also find it strange that only the very first two members with 'Employee' hierarchy are impacted.

If(
User().FullName in MemberCollection.UsrNm, Set(varlsRoster, true)

)

[JR-BejeweledOne]

In my apps I always set a variable onStart that loads either the user displayName or their email and then use the variable for comparisons when needed.

That being said, the username that you retrieve onStart must match the username as it exists in MemberCollection.UsrNm.

What is MemberCollection, is it a collection retrieved when the app is loaded?   And where is it getting the information in the UsrNm column?

I would populate a variable with one of the values and display it in a label to make sure it's what you expect and compare it against the value you are using for comparison.

You could set your label text something like this:   Set(varXXX, Filter(First(MemberCollection, UserNm)))

[Anonymous]

I agree with all you've said.

What you have described is how I've set it up. I'm pulling the Full Name from the employee server. I have mimicked EVERY full name to column FullNm in the MemberList and created a MemberCollection from which the data is being pulled.

Again, EVERYTHING has worked for everyone (about 8 testers so far) except the two with hierarchy 'Employee'; and it may have nothing to do with that. It is, however, the only commonality I've identified to this point. 

I've done the 'label' and 'button' thing. Here they are; Label one is varIsRoster; Label to is User's hierarchy. The example is my test identity in the system, and the data is accurate.

I won't be able to validate the name across the top of the 'Employee' member's screen until next week. I'll place another label for Office365Users.MyProfileV2().displayName and see what each provides as content.

That aside, I'm at a loss as to why just these two are getting this functionality; its not really an error. With this in place - !varIsRoster, the system is seeing they are not on the 'roster', or the Member List/Collection, which we know is not correct. Their names and all their documents come up when a managers looks in at them.