Delegation issue, Only display current logged in user and Count Rows

[syhrh]

Hi, I created this column chart based on the Application Record list.

I want the chart only display based on user logged in so I put the formula in the App.OnStart

Set(CurrentUser, Office365Users.MyProfile().DisplayName);
Set(CurrentUserData, LookUp('Application Record', CurrentUser = 'Employee Name'.DisplayName) );

And I use this formula, it works but it has delegation warning.

Will it be okay because it works even though with the delegation warning? Does the current user logged-in formula I put in is correct and will only display the number in the chart based on the current user?

Thank you.

[jcfDaniel]

Hi,

The delegation warning means that power apps can´t push the job to the datasource and has to it itself. This means the server will all the rows to the app, up to the delegation limit (standard 500 but you can change up to 2000). To be on the safe side, delegation should be dealt with but if you decide you are ok with it and that ypour table will not grow past the limit...

One other thing you could do is to make collections OnStart, lets say 3 collections: colApproved, colRejected and colCancelled and then count the rows on those.

[syhrh]

@jcfDaniel Thank you for your explanation.

I tried using your method and it works. However, I don't know how to put only the current user logged in into the formula.

Set(CurrentUser, Office365Users.MyProfile().DisplayName);
Set(CurrentUserData, LookUp('Application Record', CurrentUser = 'Employee Name'.DisplayName) );
ClearCollect(colApproved,Filter('Application Record',CurrentUser,'Approval Status'.Value="Approved"));
ClearCollect(colRejected,Filter('Application Record',CurrentUser,'Approval Status'.Value="Rejected"));
ClearCollect(colCancelled,Filter('Application Record',CurrentUser,'Approval Status'.Value="Cancelled"))

It has errors. How to fix it?

[jcfDaniel]

Hi, 

It should be something like this:

ClearCollect(

        colApproved,

       Filter(

            'Application Record',

           'Employee Name'.DisplayName = CurrentUser && 'Approval Status'.Value="Approved"

       )

)

And this one shouldn't be necessary: Set(CurrentUserData, LookUp('Application Record', CurrentUser = 'Employee Name'.DisplayName) )

[martijnA · Accepted solution]

ClearCollect(colConsolidated,Blank());
Set(CurrentUser,Office365Users.MyProfileV2());
ClearCollect(colApproved,Filter('Application Record',CurrentUser,'Approval Status'.Value="Approved",'Employee Name'.Email=CurrentUser.mail));
ClearCollect(colRejected,Filter('Application Record',CurrentUser,'Approval Status'.Value="Rejected",'Employee Name'.Email=CurrentUser.mail));
ClearCollect(colCancelled,Filter('Application Record',CurrentUser,'Approval Status'.Value="Cancelled",'Employee Name'.Email=CurrentUser.mail));
Collect(colConsolidated,colApproved,colRejected,colCancelled)

This will create 3 collections that only show if it is for the current user and merges them into a new collection called "colConsolidated"

Please ensure you use V2 for connectors if it is available AND don't use the displayname/fullname. On smaller businesses you wont see these attributes duplicated, but on bigger ones it would. Emails however should be unique.

Did this answer help you in any way? Consider to "Accept as Solution" and give a "Thumbs Up"

[syhrh]

@martijnA 

I got this error.

[syhrh]

@jcfDaniel it works, thank you. But as @martijnA said, using displayName instead of email could be duplicated so I should use email instead right? If it's email, then how to set it?

[jcfDaniel · Accepted solution]

Yes, @martijnA is right you could get 2 names that are the same (unless you enforce unique values, maybe [sahrepoint?])

To use the email:

Set(CurrentUser, User().Email) and the condition in the filter should be something like : 'Employee Name'.Email = CurrentUser

[martijnA]

I forgot to remove one of your CurrentUser filters

ClearCollect(colConsolidated,Blank());
Set(CurrentUser,Office365Users.MyProfileV2());
ClearCollect(colApproved,Filter('Application Record','Approval Status'.Value="Approved",'Employee Name'.Email=CurrentUser.mail));
ClearCollect(colRejected,Filter('Application Record','Approval Status'.Value="Rejected",'Employee Name'.Email=CurrentUser.mail));
ClearCollect(colCancelled,Filter('Application Record','Approval Status'.Value="Cancelled",'Employee Name'.Email=CurrentUser.mail));
Collect(colConsolidated,colApproved,colRejected,colCancelled)

As you can see, i dont set that variable to a displayname or email. im collecting that whole record. Why? That way you can reuse that variable for any of the other properties that is now collected into that variable

[martijnA]

@jcfDaniel 

By the looks of his original filter he is using a "person field". technically he could still enforce unique values there, but issue is that a person field is a record, and accordingly 2 people with exactly the same name (but who are different persons) would be treated as unique.