Hide non-address1 Account address columns from view and filter builders
Short answer
D Disable the Search option on the other Account address columns so only address1 columns are available when users create views and filters.
Question
Users must be able to view only the address1 columns in the Account table.
You need to ensure other address columns are not visible to users when creating views and filters.
What should you do?
Key Takeaways
This question tests the difference between Dataverse column-level security and the column Searchable property; the trap is assuming security or business rules remove a column from Advanced Find and view filter builders.
In Power Apps/Dataverse, the Searchable column setting controls whether a column appears in Advanced Find and view filters. This page explains why disabling Search on the non-address1 Account columns (D) is the correct fix.
Common mistake: A is the most plausible wrong answer: column-level security sounds like hiding columns, but it restricts data access and does not reliably remove the columns from the view/filter column picker, while also being overbroad when read access is removed for all users.
Expert Analysis
The control is Dataverse column metadata, not data security
The decisive requirement is not merely that users cannot read the values in the other address columns; it is that those columns must not be visible while users create views and filters. In a model-driven Power Apps/Dataverse environment, that design-time discoverability is governed by the column's Searchable setting, often shown as Search. Setting it to No for the non-address1 address columns removes them from Advanced Find and view/filter column pickers while the schema and stored data remain intact.
Why option D fits
Option D, disabling the Search option for those columns, matches that behaviour exactly. Users can still use address1 columns, but Address 2 and any other non-address1 address columns are not offered when building views and filters. The change is targeted and reversible.
Why the alternatives fail
A is the main trap. Column-level security can restrict who can read or update a field's data, but it is a security boundary, not a clean way to hide metadata from view and filter builders; the columns can still appear in Advanced Find, and removing read access from all users is overly broad. B is also misleading: business rules can hide fields on forms, but they do not control the Advanced Find/view filter column list. C is destructive: deleting columns removes schema and data and can break forms, flows, integrations, and reports. The discussion around this question converges on the same distinction: security governs data access, while Searchable governs whether a column is offered in Advanced Find. The correct option is therefore D.
Exam Strategy
For Power Apps/Dataverse questions, separate data visibility from design-time column availability. If the stem says users should not see columns while creating views or filters, look for the column Searchable/Search option rather than security roles or business rules. Column-level security can still leave columns in Advanced Find, and business rules affect forms. Also reject destructive options like deleting schema columns unless explicitly required.
Frequently Asked Questions
What does the Searchable setting do on a Dataverse Account column?
Why not use column-level security to hide Address 2 from view builders?
Can business rules hide columns in Advanced Find or view filters?
Discussion 2 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 2
-
aed747e 👍 4 Answered DDisabling the Searchable property on specific columns removes them from Advanced Find, which prevents users from seeing, selecting, or filtering by them when constructing custom Views in Dataverse. Not A: Column security restricts data viewing, but columns still appear when building views or filters.
-
exam_upskill 👍 1 Answered DD. Disable the Search option for the columns.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.