You have a Power BI dataset that has only the necessary fields visible for report development. You need to ensure that end users see only 25 specific fields that they can use to personalize visuals…

Creating a new role from Tabular Editor is primarily for implementing row-level security (RLS) or object-level security (OLS), which restricts data access or visibility of objects entirely, not for presenting a curated view for personalization.

Hiding all fields would make them unavailable for both report development and end-user personalization, which contradicts the requirement for developers to see all necessary fields.

Object-level security (OLS) restricts access to sensitive tables or columns for specific roles, effectively making them invisible or inaccessible. While it can hide fields, it's a security mechanism, not primarily a way to curate a specific subset for personalization without affecting developer view.

Creating a new perspective in Tabular Editor allows you to define a specific subset of tables, columns, and measures from the dataset that will be visible to end-users for tasks like personalizing visuals. This enables different views of the dataset for different user needs without altering the underlying model for report developers.