You have a form that displays a custom field from an entity. A customer wants to restrict users from filtering on the custom field. You need to prevent users from filtering the field in Advanced Find.

The correct answer is C. a searchable field on the Field Properties form. Setting Searchable property to No, makes the field disappear from the available fields for the Filter configuration, but it won't hide the field when adding columns to the view. This property has no impact on behaviour of the Global and Quick Find Search. https://community.dynami

Configure Microsoft Dataverse

Question

You have a form that displays a custom field from an entity. A customer wants to restrict users from filtering on the custom field. You need to prevent users from filtering the field in Advanced Find. What should you modify?

Options

AFields in the Edit Filter Criteria option of the Quick Find view
Bthe Field Security field on the Field Properties form
Ca searchable field on the Field Properties form
DFields in the Add Find Columns option of the Quick Find view

How the community answered

(46 responses)

A
9% (4)
B
2% (1)
C
83% (38)
D
7% (3)

Explanation

Setting Searchable property to No, makes the field disappear from the available fields for the Filter configuration, but it won't hide the field when adding columns to the view. This property has no impact on behaviour of the Global and Quick Find Search. https://community.dynamics.com/365/b/dynamics365apps/posts/kb-understanding-dynamics-365- field-s-searchable-property

Topics

#Dataverse Field Properties#Advanced Find#Model-Driven Apps#Filtering Restrictions

Community Discussion

No community discussion yet for this question.

Full PL-200 Practice