Need Help: OnStart Collection for User Permissions in Dataverse Table, displaying "This datatype is unsupported for Evaluation"

[PowerApp_Chaos]

Hello,

Background:

I am working to create a timetracking powerapp for our department to use in entering time weekly spent in projects and other operational and administrative activities.  

I am working on setting up the OnStart application variables, many of which will be used in establishing the users permissions, and necessary dropdowns within the app.  I have a table in Dataverse where I have entered in user data (Email, Employee ID, Name) along with 3 columns that are "yes/no" type for their permissions as a timesheetresource, manager, and administrator.  

My goal is to pull the user into the collection, get their info from this table, and use an IF statement to define their permissions within the app.

However, what I noticed after getting the collection setup is that the fields in Dataverse setup as boolean ("yes/no" in dataverse) are showing in the collection as "This data type is unsupported for evaluation".  

QUESTION:

Can someone advise how I can pull into the collection these boolean values from dataverse, or if there is another way I should go about setting this up?

Also, as a side-note, I tried comparing the email in the table using filter against the email collected in the above collection variable called colUser, however when I attempted to do so it gave an error that it cant pull from a table.  So instead I simply pulled in the users email into the filter criteria.  I imagine this is because you can't use an array in a filter comparison operation.

[Amik]

@PowerApp_Chaos - I am not clear on where/how you're going to use your Yes/No columns, but you can certainly return their values from that Collection.

E.g. for the Items property of a Gallery control you can use:

Filter(
    colPermissions,
    crb01_ismanagement = 'Is Management (Your Table Plural Name)'.Yes
)

Or in a LookUp:

LookUp(
    colPermissions,
    'Is Management'
)

[PowerApp_Chaos]

@Amik, I need to use this in the collection OnStart to get the users row from the permissions table, and identify what permissions they have

Each column is a Yes/No checkbox in the Dataverse where the admin can check whether the listed user should have access in the timetracking app as a timesheet submitter, a manager, or an administrator, by selecting YES or NO.

How can I get it to show the Yes/No value contained within this field in the collection?  When I load the table those fields/columns only show up with that error message, that they can't be evaluated

[Amik]

@PowerApp_Chaos - That is not an error message. It simply means that the value of a complex type cannot be displayed for you in the preview bar (because they are complex data types). Look at the examples I already gave you, they will return the value of those data types.

Suppose for example I want to check if the logged in user's record has "Is Management" checked, I can simply use:

LookUp(
    colPermissions,
    'Your People Field'.'Primary Email' = User().Email,
    'Is Management'
)

[PowerApp_Chaos]

I tried this, as a test, against the table in Dataverse, and it doesn't work.  You can see below that when I assign the lookup to a variable it returns the value "This Datatype is Unsupported for Evaluation"

[Amik]

@PowerApp_Chaos - apply "varUserOne" onto the Text property of a Label control and observe what happens. 

Or if you must display the value in the Preview bar, use:

Set(
    varUserOne,
    Text(
        LookUp(
            REF_Timetracking_UserPermissions,
            ResourceEmail = Lower(User().Email),
            IsManagement
        )
    )
)

[PowerApp_Chaos]

Sorry, I appreciate your help,but it still does not work, even when applied to a label

It just shows up as a blank value

[PowerApp_Chaos]

Apologies, I refreshed my PowerApp browser and it suddenly started working.  For some reason it wasn't showing previously no matter what I did,

[Amik]

@PowerApp_Chaos - has your question now been resolved?

On a separate note, I would suggest creating custom security roles and assigning relevant users to those roles. You can then identify the security role for the current logged user of the app session and use that to run whatever logic you need.