Blocking Advanced Find Filtering on a Custom Field
Short answer
B Clear the Searchable checkbox on the custom field's Field Properties form so the field is no longer exposed as a filterable attribute in Advanced Find.
Question
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?
Key Takeaways
The question tests which setting governs Advanced Find exposure; the trap is confusing the Quick Find view's find/filter columns, which only affect the Quick Find search box, not Advanced Find.
In model-driven apps, the Searchable checkbox on a field's Field Properties determines whether that field is exposed as a filterable attribute in Advanced Find. Clearing Searchable on the custom field removes it from Advanced Find filter criteria, which is the correct way to honor the customer's restriction.
Common mistake: The most common wrong answers are A and C — testers assume the Quick Find view's Edit Filter Criteria or Add Find Columns govern all filtering. Those options only shape what Quick Find searches and which conditions it applies; they have no effect on Advanced Find.
Expert Analysis
Why the Answer Is Correct
Every Dataverse field carries an "Additional Properties → Searchable" flag on its Field Properties form, and this flag is exactly what publishes the attribute to the Advanced Find metadata. When Searchable is cleared, the field stops appearing in the Advanced Find filter tree and in the filterable column list, so users can no longer build conditions on it. This is a per-field, solution-level change and it persists for all users regardless of security roles, which is what a blanket customer restriction requires.
Why the Other Options Are Wrong
"Fields in the Add Find Columns option of the Quick Find view" controls which columns the Quick Find search box scans when a user types a search string; removing a column there simply narrows search scope and still leaves the field filterable in Advanced Find. "Fields in the Edit Filter Criteria option of the Quick Find view" defines the default conditions applied to records returned by Quick Find; it changes search results, not whether the field is exposed as a filter in Advanced Find. Neither Quick Find setting removes the attribute from the Advanced Find filter picker, so neither satisfies the requirement.
Community Comment Notes
The single comment on this item simply restated the choice "B. a searchable field on the Field Properties form" without adding rationale, so it aligns with the independent analysis but offers no additional evidence to weigh.
Exam Strategy
On model-driven questions, remember the split of responsibilities: Quick Find view settings govern the search box, while the field's Searchable property governs Advanced Find and other metadata-based exposure. Read carefully whether the scenario mentions Advanced Find, the search box, or search relevance before picking a view setting.
Frequently Asked Questions
Why does clearing Add Find Columns not stop Advanced Find filtering?
Does turning off Searchable hide the field from the form itself?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
exam_upskill 👍 1 Answered BB. a searchable field on the Field Properties form
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.