Power-bi-agentic-development c-sharp-scripting
Writing and executing C# scripts and macros against Power BI semantic models using Tabular Editor 2/3. Automatically invoke when the user mentions "C# script", "Tabular Editor script", "TOM scripting", "MacroActions.json", "XMLA", or asks to "automate model changes", "bulk update measures", "create calculation groups", "write a macro", "format DAX expressions", "manage model metadata".
git clone https://github.com/data-goblin/power-bi-agentic-development
T=$(mktemp -d) && git clone --depth=1 https://github.com/data-goblin/power-bi-agentic-development "$T" && mkdir -p ~/.claude/skills && cp -r "$T/plugins/tabular-editor/skills/c-sharp-scripting" ~/.claude/skills/data-goblin-power-bi-agentic-development-c-sharp-scripting && rm -rf "$T"
plugins/tabular-editor/skills/c-sharp-scripting/SKILL.mdC# Scripting for Tabular Editor
Expert guidance for writing and executing C# scripts to manipulate Power BI semantic model metadata using Tabular Editor 2/3 CLI or the Tabular Editor IDE.
When to Use This Skill
Activate automatically when tasks involve:
- Writing C# scripts for Tabular Editor
- Bulk operations on model objects (measures, columns, tables)
- Creating or modifying calculation groups
- Managing model security (roles, RLS, OLS)
- Formatting DAX expressions
- Automating repetitive model changes
- Querying model metadata via TOM API
- Building interactive scripts with user input dialogs
Critical
- Every statement must end with
(semicolon required by C#); - Use double quotes
for strings and escape with"
when needed\ - Use forward slashes
in DisplayFolder paths (auto-converted to/
)\ - Always add
statements for debugging - script stops at error pointInfo() - Test scripts on non-production models first
- Changes are undoable with Ctrl+Z in the Tabular Editor UI
C# Version Support
| Environment | C# Version | Notes |
|---|---|---|
| Tabular Editor 2 | Default compiler | Older C# syntax |
| Tabular Editor 3 | Roslyn | Supports up to C# 12 with VS2022 |
| TE2 with Roslyn | Configurable | Set in File > Preferences > General |
To use newer C# features in TE2, configure Roslyn compiler path in preferences.
Default Imports and Assemblies
Auto-Imported Namespaces
Scripts automatically have these
using statements applied:
using System; using System.Linq; using System.Collections.Generic; using Newtonsoft.Json; using TabularEditor.TOMWrapper; using TabularEditor.TOMWrapper.Utils; using TabularEditor.UI;
Pre-Loaded Assemblies
These .NET assemblies are loaded by default:
System.DllSystem.Core.DllSystem.Data.Dll
(for UI dialogs)System.Windows.Forms.DllMicrosoft.Csharp.DllNewtonsoft.Json.DllTomWrapper.DllTabularEditor.ExeMicrosoft.AnalysisServices.Tabular.Dll
Adding External Assemblies
// Assembly references must be at the very top of the file: #r "System.IO.Compression" #r "System.Drawing" // Using statements come after assembly references: using System.IO.Compression; using System.Drawing;
Prerequisites
For Tabular Editor CLI
| Requirement | Description |
|---|---|
| Tabular Editor 2 CLI | Download from GitHub releases |
| XMLA Read/Write | Enabled on Fabric capacity or Power BI Premium |
| Azure Service Principal | For XMLA connections (see authentication.md) |
Environment Variables (for XMLA)
AZURE_CLIENT_ID=<app-id> AZURE_TENANT_ID=<tenant-id> AZURE_CLIENT_SECRET=<secret>
Execution Methods
1. Tabular Editor CLI
# Inline script TabularEditor.exe "WorkspaceName/ModelName" -S "Info(Model.Database.Name);" # Script file TabularEditor.exe "WorkspaceName/ModelName" -S "script.csx"
2. Connection Types
| Type | Format | Example |
|---|---|---|
| XMLA | | |
| Local BIM | | |
| Local TMDL | | |
| PBI Desktop | | |
Core Objects
The Model
Object
ModelAccess any object in the loaded Tabular Model:
Model // Root model object Model.Tables // All tables Model.Tables["Sales"] // Specific table Model.AllMeasures // All measures across all tables Model.AllColumns // All columns across all tables Model.Relationships // All relationships Model.Roles // All security roles Model.CalculationGroups // All calculation groups Model.Perspectives // All perspectives Model.Cultures // All translations/cultures Model.Expressions // All M expressions (shared queries) Model.DataSources // All data sources
The Selected
Object
SelectedAccess objects currently selected in the TOM Explorer (IDE only):
// Plural form - collections (safe even when empty) Selected.Tables // Selected tables Selected.Measures // Selected measures Selected.Columns // Selected columns Selected.Hierarchies // Selected hierarchies // Singular form - single object (error if not exactly one selected) Selected.Table // The single selected table Selected.Measure // The single selected measure Selected.Column // The single selected column // Set properties on multiple objects at once Selected.Measures.DisplayFolder = "Test"; Selected.Columns.IsHidden = true; // Bulk rename with pattern Selected.Measures.Rename("Amount", "Value");
When a Display Folder is selected, all child items are included in the selection.
LINQ Fundamentals
LINQ is essential for filtering and transforming TOM collections. See
for the full method table, lambda syntax, and examples.references/linq-reference.md
Key methods:
Where(), First(), FirstOrDefault(), Any(), All(), Count(), Select(), OrderBy(), ForEach(), ToList().
// Common pattern: filter, chain, act Model.AllMeasures .Where(m => m.Name.Contains("Revenue")) .Where(m => string.IsNullOrEmpty(m.FormatString)) .ForEach(m => m.FormatString = "$#,0");
Helper Methods
See
for the complete reference including Output() variations, file operations, property export/import, interactive selection dialogs, DAX formatting/execution, and macro invocation.references/helper-methods.md
| Method | Purpose |
|---|---|
| Display info popup (CLI: writes to console) |
| Display warning popup |
| Display error popup and stop script |
| Display detailed object inspector dialog |
/ | File I/O |
/ | TSV export/import |
/ | Interactive selection (IDE only) |
/ | DAX formatting |
/ | DAX execution (connected) |
WinForms UI Patterns
For interactive dialogs (input forms, dropdowns, multi-select), see
. Key setup: references/winforms-dialogs.md
#r "System.Drawing", ScriptHelper.WaitFormVisible = false;
Quick Reference
Core Patterns
Add a Measure:
var m = Model.Tables["Sales"].AddMeasure("Total Revenue", "SUM(Sales[Amount])"); m.FormatString = "$#,0"; m.DisplayFolder = "Key Metrics"; m.Description = "Total sales revenue"; Info("Added: " + m.Name);
Iterate Tables/Columns:
foreach(var t in Model.Tables) { foreach(var c in t.Columns.Where(c => c.Name.EndsWith("Key"))) { c.IsHidden = true; } } Info("Hidden key columns");
Conditional Operations:
foreach(var m in Model.AllMeasures) { if(m.Name.Contains("Revenue")) m.FormatString = "$#,0"; if(m.Name.Contains("Rate")) m.FormatString = "0.00%"; }
Create Calculation Group:
var cg = Model.AddCalculationGroup("Time Intelligence"); cg.Precedence = 10; var ytd = cg.AddCalculationItem("YTD", "CALCULATE(SELECTEDMEASURE(), DATESYTD('Date'[Date]))"); var prior = cg.AddCalculationItem("Prior Year"); prior.Expression = @" CALCULATE( SELECTEDMEASURE(), DATEADD('Date'[Date], -1, YEAR) ) "; Info("Created calculation group");
TOM API Quick Reference
| Object | Access | Common Properties |
|---|---|---|
| Model | | , , |
| Table | | , , , |
| Measure | | , , , |
| Column | | , , , |
| Relationship | | , , , |
| Role | | , |
| Hierarchy | | , , |
| Partition | | , , |
| Perspective | | Objects have |
| Culture | | Objects have |
Object Type Reference
Detailed documentation for each object type in
object-types/:
- Table CRUD, properties, partitionstables.md
- Column types, properties, sortingcolumns.md
- Measure creation, formatting, organizationmeasures.md
- Relationship managementrelationships.md
- Calculation groups and itemscalculation-groups.md
- Roles, RLS, OLS configurationroles.md
- Hierarchy and level managementhierarchies.md
- Partition types and configurationpartitions.md
- Perspective membershipperspectives.md
- Culture and translation managementtranslations.md
- Custom metadata annotationsannotations.md
Example Scripts
180 working
.csx scripts organized by category in examples/. Before writing a script from scratch, check if a relevant example already exists -- read the example, adapt it to the task, and modify as needed.
| Category | Scripts | Description |
|---|---|---|
| 8 | Model initialization, batch updates, clean names, sync folders, validate |
| 2 | Time intelligence, currency conversion |
| 20 | Data types, hiding, sorting, encoding hints, cardinality, properties |
| 4 | Add/delete cultures, list, modify translations |
| 8 | Organize by type, clear, rename, add/remove folders |
| 5 | Execute DAX, scalar queries, table queries, column sizes, optimize |
| 8 | Format measures, calculated columns/tables, KPIs, detail rows |
| 6 | Apply by name/pattern, custom formats, dynamic format strings |
| 4 | Add/delete/list/modify shared M functions |
| 4 | Add/delete/list/modify hierarchies |
| 4 | Add/delete/list/modify KPIs |
| 18 | Full CRUD, time intelligence, bulk create, move, hide/unhide |
| 10 | Properties, compatibility level, dependencies, refresh, export stats |
| 6 | Refresh, find-replace M, incremental refresh, hybrid tables |
| 4 | Add/delete/list/modify perspectives |
| 5 | Create, naming conventions, RI violations, integrity, properties |
| 7 | Add/delete roles, members, RLS, OLS configuration |
| 6 | Named expressions, range parameters, M functions |
| 15 | Bar charts, bullet charts, dumbbells, lollipops, waterfall, jitter |
| 36 | All table types (import, DirectQuery, Direct Lake, calculated, field parameter, date), refresh policies, RLS/OLS, properties |
Common Workflows
See
for complete workflow scripts: bulk format measures, create time intelligence measures, configure RLS, audit hidden objects. Also check references/common-workflows.md
examples/ for 180 working .csx scripts before writing from scratch.
Debugging & Troubleshooting
Script Doesn't Complete
Add
Info() checkpoints to find where script fails:
Info("Step 1: Starting"); var table = Model.Tables["Sales"]; Info("Step 2: Got table"); var measure = table.AddMeasure("Test", "1"); Info("Step 3: Added measure"); // If this doesn't appear, AddMeasure failed
Object Not Found
Check existence before accessing:
if(Model.Tables.Contains("Sales")) { var table = Model.Tables["Sales"]; // ... } else { Error("Table 'Sales' not found"); } // Or use FirstOrDefault var table = Model.Tables.FirstOrDefault(t => t.Name == "Sales"); if(table == null) { Error("Table not found"); }
Changes Not Appearing
- XMLA operations may take 2-5 seconds to sync
- Refresh Power BI Desktop connection after changes
- Check for silent errors (add
after each operation)Info()
TE2/TE3 Compatibility
Use preprocessor directives for version-specific code:
#if TE3 // TE3-specific code (version 3.10.0+) Info("Running in Tabular Editor 3"); #else // TE2 fallback Info("Running in Tabular Editor 2"); #endif
Check version at runtime:
var majorVersion = Selected.GetType().Assembly.GetName().Version.Major; if(majorVersion >= 3) { // TE3 code }
Best Practices
- Add Info() statements - Track script execution and catch errors early
- Check object existence - Use
or.Contains()
before accessing.Any() - Use bulk operations - Single script with loops is faster than multiple scripts
- Test on dev models - Never test new scripts on production
- Use @"..." for DAX - Multi-line strings for DAX expressions
- Format with FormatDax() - After creating measures/columns
- Set DisplayFolder with / - Forward slashes auto-convert to backslashes
- Hide the wait spinner -
for UI dialogsScriptHelper.WaitFormVisible = false;
Additional Resources
Reference Files
- Detailed API docs per object typeobject-types/
- 180 workingexamples/
scripts across 20 categories; always check here before writing from scratch.csx
Fetching Docs
To retrieve current TOM API reference docs, use
microsoft_docs_search + microsoft_docs_fetch (MCP) if available, otherwise mslearn search + mslearn fetch (CLI). Search based on the user's request and run multiple searches as needed to ensure sufficient context before proceeding.