Programmatically Change Semantic Model Columns
You have a Fabric tenant that contains a semantic model. The model contains 15 tables. You need to programmatically change each column that ends in the word Key to meet the following requirements: • Hide the column. • Set Nullable to False • Set Summarize By to None. • Set Available in MDX to False. • Mark the column as a key column. What should you use?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests knowledge of external tools for semantic models; the common trap is choosing Power BI Desktop, which requires manual effort for bulk changes instead of programmatic scripting.
Identify the correct tool for programmatically modifying semantic model columns in a Fabric tenant. This page establishes Tabular Editor as the best choice for bulk metadata updates based on naming conventions.
Choosing Microsoft Power BI Desktop because it can set these properties, but it cannot easily do so programmatically in bulk based on a naming convention.
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
Tabular Editor (Option C) is the premier tool for programmatically modifying the Tabular Object Model (TOM) of a Power BI or Fabric semantic model. It supports Advanced Scripting (C#) that allows users to iterate over all tables and columns, filter by naming conventions (like columns ending in "Key"), and apply bulk metadata changes such as hiding columns or setting the SummarizeBy property. This directly satisfies the requirement to "programmatically change" multiple columns efficiently.Why the Other Options Are Wrong
Microsoft Power BI Desktop (Option A) allows setting these properties, but doing so for 15 tables manually is tedious and not programmatic. ALM Toolkit (Option B) is designed for source control and deployment comparisons (Application Lifecycle Management), not for authoring or scripting metadata changes. DAX Studio (Option D) is a tool for DAX query optimization, performance tuning, and capturing server traces, not for modifying semantic model metadata.Community Comment Notes
Community members correctly identified Tabular Editor's scripting capabilities for bulk changes, noting that Power BI Desktop "doesn't offer functionalities for bulk programmatic changes based on naming conventions." Another user questioned why Power BI Desktop is incorrect, failing to recognize the distinction between manual property updates and programmatic bulk operations.Official Reference
Exam Strategy
When a question specifies "programmatically" or "bulk" changes to a semantic model's metadata, immediately look for Tabular Editor as the solution. DAX Studio is for queries, ALM Toolkit is for deployment comparisons, and Power BI Desktop is for manual modeling.
Related Analysis
Practice All DP-600 Questions
Access 115 questions with complete answers and detailed explanations.
View Full DP-600 Practice Test →