You have a Power Platform solution that uses Common Data Service. You need to secure all fields that support field-level security. Which field can you secure?

The correct answer is D. cr7b_accountid. In Power Platform (Dataverse), field-level security (FLS) can only be applied to custom fields and a limited set of specific system fields - it cannot be applied to core system fields that are required for platform functionality. 'createdon' (A) is a system-generated timestamp…

Design business solutions

Question

You have a Power Platform solution that uses Common Data Service. You need to secure all fields that support field-level security. Which field can you secure?

Options

Acreatedon
Baccountid
Cowninguser
Dcr7b_accountid

How the community answered

(33 responses)

B
6% (2)
C
3% (1)
D
91% (30)

Explanation

In Power Platform (Dataverse), field-level security (FLS) can only be applied to custom fields and a limited set of specific system fields - it cannot be applied to core system fields that are required for platform functionality. 'createdon' (A) is a system-generated timestamp field and does not support FLS. 'accountid' (B) is the primary key field of the Account entity; primary key fields are excluded from FLS. 'owninguser' (C) is a system ownership field that also cannot be secured via FLS. 'cr7b_accountid' (D) is a custom field, identifiable by its publisher prefix ('cr7b_'). Custom fields are eligible for field-level security profiles. Therefore, D is the only field that can be secured using field-level security.

Topics

#Field-Level Security (FLS)#Dataverse Security#Custom Fields#Power Platform Security

Community Discussion

No community discussion yet for this question.

Full PL-100 Practice