{"id":1293,"date":"2026-08-04T15:53:14","date_gmt":"2026-08-04T14:53:14","guid":{"rendered":"https:\/\/knitteddata.com\/?p=1293"},"modified":"2026-08-11T11:25:04","modified_gmt":"2026-08-11T10:25:04","slug":"knit-with-c-scripting-in-tabular-editor","status":"publish","type":"post","link":"https:\/\/knitteddata.com\/index.php\/2026\/08\/04\/knit-with-c-scripting-in-tabular-editor\/","title":{"rendered":"Knit with C#: Scripting in Tabular Editor"},"content":{"rendered":"\n

On my blog, you can already find a post where I show how to set everything up for scripting in Tabular Editor and explain how to work with the model. If you haven\u2019t read it yet, click HERE<\/a>.<\/p>\n\n\n\n

In this post, I want to share how I use scripting in Power BI to make my life easier.<\/p>\n\n\n\n

I like to use scripts to keep my semantic models consistent. They help me make sure that models follow the same structure, naming conventions are applied across different projects, and everyone who uses my models for reporting or ad hoc analysis can easily find what they need.<\/p>\n\n\n\n

Because once you get used to a clean structure, you really do not want to hand-knit every measure one by one anymore.<\/p>\n\n\n\n

Creating measures automatically from columns<\/strong><\/h2>\n\n\n\n

The first thing I often use scripts for is creating measures automatically from columns.<\/p>\n\n\n\n

Most of the time, I add some information to the column names so I can quickly identify which columns should become measures. In this example, I added the prefix KPI <\/mark>to the columns in the Sales <\/mark>table that I want to turn into measures.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Now let\u2019s open Tabular Editor, go to the C# Script<\/strong> tab, and paste the following code.<\/p>\n\n\n\n

The script will go through all columns in the Sales <\/mark>table and look for columns that contain KPI <\/mark>. For each of those columns, it will create a measure with a simple SUM()<\/mark> expression.<\/p>\n\n\n\n

For that, I use the .AddMeasure(Name, DAX Expression, DisplayFolder)<\/mark> function, which is available for every table in the model.<\/p>\n\n\n\n

Run the code with the green arrow, and remember to save your changes with the disk icon. Otherwise, when you go back to Power BI Desktop, the measures will not be there.<\/p>\n\n\n\n

\/\/ Table where I want to save my measures\nvar MeasuresTable = Model.Tables[\"_Measures\"];\n\n\/\/ Sales table where I can find columns that I want to turn into measures\nvar kpiSourceTable = Model.Tables[\"Sales\"];\n\n\/\/ Loop through all columns in the Sales table\nforeach(var column in kpiSourceTable.Columns)\n{\n    \/\/ Condition to only create measures for columns containing \"KPI \"\n    if (column.Name.Contains(\"KPI \"))\n    {\n        \/\/ Using the .AddMeasure() function\n        MeasuresTable.AddMeasure(\n            column.Name,                                  \/\/ Name\n            \/\/ column.DaxObjectFullName returns the TableName[ColumnName] combination.\n            \"SUM(\" + column.DaxObjectFullName + \")\",      \/\/ DAX expression\n            \"Generated from Columns\"                      \/\/ Display folder\n        );\n    }\n}<\/code><\/pre>\n\n\n\n