Where Should You Create a View for All Users in Dataverse?
Your organization does not permit the use of custom code for solutions. You need to create a view that can be viewed by all users in an organization. Where should you create the view?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests where system views are authored in Dataverse, and the common trap is choosing the runtime List view of the table because that is where users see and create personal views.
In Microsoft Dataverse, a view that all users can see is a system view authored from the table component of a solution. This PL-200 answer guide confirms D and explains why Templates, System Settings, and the runtime list view are not the right creation points.
Selecting C (List view of the table) because it sounds like the view location in an app; however, that surface is for personal views and does not make a view available to all users as a solution component.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
In Dataverse, a view that every user can see is a system view, and system views are created from the table's design surface, not from an individual user's list. The Table component of a solution is that design surface: when you add a table to a solution and open it, you can define columns, forms, and views, and the view becomes part of the solution. Because this is pure configuration—no plug-ins, JavaScript, or custom controls are required—it satisfies the organization's no-custom-code policy while making the view available to all users in the environment. The community consensus reinforces this: one learner wrote, "For the tenth time D. Table component of a solution," and another explained that creating the view there "ensures that the view can be accessed by all users in the organization."Why the Other Options Are Wrong
The Templates area (A) is used for templates such as email or document templates, not for table views, so it cannot produce an organization-wide view. System Settings (B) controls environment-wide configuration options such as formats and auditing, and it does not contain a view designer for Dataverse tables. The List view of the table (C) is the runtime grid users see in an app; creating a personal view there makes it visible only to that user until it is shared, and it is not the solution-aware design surface the question requires. Choosing C confuses where a view is used with where a system view is authored, which is exactly the trap PL-200 sets.Community Comment Notes
All voters selected D, and the top comment is blunt: "For the tenth time D. Table component of a solution." Masbee mentions virtual tables and external data providers, which is accurate Dataverse knowledge but unrelated to where to author a system view. Killionb12 notes that building the view in the table component "ensures that the view can be accessed by all users in the organization" and lets it ship inside a managed solution for easier deployment. No commenter defends A, B, or C, so the community signal aligns with the official Dataverse design surface.Official Reference
Exam Strategy
When a PL-200 question mentions no custom code and a view for all users, map it directly to system views created in the table component of a solution. Eliminate Templates, System Settings, and personal list-view options because they either serve other purposes or create user-scoped views.
Frequently Asked Questions
Why is the List view of the table (C) not the correct place to create an organization-wide view?
The list view in an app is where users see records and can create personal views. An organization-wide system view must be authored from the table component in a solution.
Does creating a system view in a Dataverse solution require custom code?
No. Views are configuration components; adding a table to a solution and creating a view in its table component uses built-in designer tools without writing code.