Power Platform Community Forum Thread Details

I need to implement column-level security on the msdyn_ocliveworkitem entity in Dataverse, to prevent access to columns that include Customer information

This table is an "activity" entity type, therefore its a pointer table, as documented here Activity table (Microsoft Dataverse) - Power Apps | Microsoft Learn

For example column msdyn_customername, this column I cannot see in the "columns" page of the msdyn_ocliveworkitem entity in Power Apps, therefore I am unsure what is the actual source entity for this column, in order to apply the column security

Can anyone please share any insights into the actual source entity and columns for all msdyn_ocliveworkitem columns, or any guidance on how to apply column-level security to this "activity" table?

TIA

Categories:

Microsoft Dataverse with Power Apps

Hello.

Base on what you wrote, I believe that you make wrong choice when you choose to create this tables as activities. Activities in Dataverse means to point in a action that was made with the customer (account or a contact) like a call, or e-mail change, information that cross for who is owner of the record, because these small actions must be visible or editable for who have access to the record.

Once yo have permission in activities, even system or customized you are allowed the work with all of them, you can sometime use a call,e-mail or whenever other activity that you have to register to you customer.

But now if you business rule, tells that you have restrictions across who create, edit or view. I would recommend to use a standard table.

Unfortunately it is not able to edit activity pointer filed to apply field level security