Upgrading the Power BI Compatibility Level — A Step-by-Step Guide
How to force Power BI to upgrade the Compatibility Level of a Semantic Model — and why this matters for complete model documentation.
published on 2026-04-02
Anyone working with Power BI will sooner or later come across the term Compatibility Level. Every Semantic Model has one, and it determines which DAX functions and features are available. New Power BI releases introduce new capabilities — but the model only gains access to them once its Compatibility Level has been raised.
In this article, I will show why an up-to-date Compatibility Level matters, how to upgrade it deliberately, and what it means for documenting a model.
What Is the Compatibility Level?
The Compatibility Level (CL) is a version number of the Analysis Services tabular model that underpins every Power BI Semantic Model. It determines which engine features and DAX functions can be used.
flowchart LR
A["Power BI Desktop Version"] -->|determines max. available| B["Compatibility Level"]
B -->|unlocks| C["New DAX Functions"]
C --> D["e.g. INFO.USERDEFINEDFUNCTIONS()"]A model created a year ago may still be on an older CL, even if it is opened with a current version of Power BI Desktop. Power BI does not automatically raise the CL — unless a feature is used that requires a newer version.
Why Does This Matter?
For Day-to-Day Work
On an older CL, certain new DAX functions are not available. For example, to use INFO.USERDEFINEDFUNCTIONS() — currently the newest INFO function (as of March 2026) — you need CL ≥ 1700.
For Model Documentation
Documenting a Semantic Model today usually means reading its metadata through the INFO functions. Which of them the model supports depends on its Compatibility Level:
| Compatibility Level | What can be read |
|---|---|
| CL ≥ 1200 | All INFO functions except INFO.USERDEFINEDFUNCTIONS. UDFs are only visible via INFO.CALCDEPENDENCY — and only those referenced by a measure or column, with limited metadata. |
| CL ≥ 1700 | All INFO functions incl. INFO.USERDEFINEDFUNCTIONS. Complete UDF metadata, including functions not (yet) used anywhere. |
For models with User Defined Functions (UDFs) the upgrade pays off twice: only from CL 1700 is the documentation of those functions complete. If running INFO.USERDEFINEDFUNCTIONS() returns an error, your model's Compatibility Level is most likely not high enough.
How the CL Upgrade Works
The core idea is simple: You need to use a feature that is not yet supported by the model's current CL. Power BI detects this and automatically raises the Compatibility Level.
As of March 2026, the newest feature that triggers a CL upgrade to 1700 is the INFO.USERDEFINEDFUNCTIONS() function. This function requires that the model supports User Defined Functions (UDFs). The easiest way to trigger this: create a temporary UDF.
flowchart LR
A["Create temporary UDF"] --> B["Power BI detects
new feature"]
B --> C["CL automatically
raised to ≥ 1700"]
C --> D["Save the model"]
D --> E["Delete UDF
(optional)"]Step-by-Step Instructions
Prerequisites
- Power BI Desktop March 2026 or newer (older versions do not support the required CL)
- Alternatively, open the already published model for editing in the Power BI Service (useful when organisational policies prevent access to the latest Power BI Desktop version)
Step 1: Open DAX Query View
In Power BI Desktop, switch to the DAX Query View tab (bottom-left in the view bar, or via View → DAX Query View).
Step 2: Create a Temporary UDF
Paste the following DAX code into the query editor and run it:
DEFINE
-- Temporary function to trigger the CL upgrade.
-- Can be deleted afterwards.
FUNCTION TempUDF = (a, b) => a + b
EVALUATE ROW("result", TempUDF(1, 2))What happens here? We define a simple function
TempUDFthat adds two numbers. This alone is enough — Power BI detects that the current CL does not support UDFs and automatically raises it to CL 1700. The query result (the value3) is incidental.
If the execution succeeds (result: 3), the CL has already been raised.
Step 3: Save the Model
Save the .pbix file (Ctrl+S). This persists the new Compatibility Level permanently.
Step 4: Delete the Temporary UDF (Optional)
The temporary function is only needed for the query execution. If it was saved as part of the model, it can be removed via the Model tab:
- In the Model view, check the Functions tab
- If
TempUDFappears there: right-click → Delete - Save again
Note: The function from the
DEFINEblock is often not saved to the model at all, since it is defined as query-scoped. It does not hurt to check, though.
Step 5: Verify
To confirm the upgrade was successful, run the following DAX query:
EVALUATE INFO.USERDEFINEDFUNCTIONS()If this command runs without errors (returning an empty or populated table), the CL upgrade is complete.
Summary: Process at a Glance
flowchart TD
A["Open Power BI Desktop
March 2026+"] --> B["Open Semantic Model
(.pbix)"]
B --> C["Open DAX Query View"]
C --> D["Run temporary UDF:
FUNCTION TempUDF = (a, b) => a + b"]
D --> E["Save model
(Ctrl+S)"]
E --> F["Optional: delete TempUDF
from model"]
F --> G["Verify:
run INFO.USERDEFINEDFUNCTIONS()"]
G --> H["✓ CL ≥ 1700 — complete
UDF metadata available"]Frequently Asked Questions
Can the CL upgrade break anything in my model?
No. Raising the Compatibility Level is forward-compatible. Existing DAX expressions, relationships, and measures remain unchanged. Only new functions are additionally made available.
Do I need to keep the temporary UDF?
No. The UDF only serves as a trigger for the upgrade. Once the model has been saved, it can be deleted without resetting the Compatibility Level.
What happens if I use an older Power BI Desktop version?
Versions before March 2026 do not support CL 1700. In that case, the query will fail with an error. Solution: update Power BI Desktop or edit the model directly in the Power BI Service (see above).
Does this also work in the Power BI Service / Fabric?
Yes. If you edit the Semantic Model directly in the Power BI Service (via the web interface with DAX Query View), you can run the temporary UDF there just the same — the CL upgrade is then performed directly in the service. This is especially handy when organisational policies prevent access to the latest Power BI Desktop version.
Tags: Power BI, Compatibility Level, DAX, User Defined Functions, UDF, Documentation, Power BI Desktop, INFO.USERDEFINEDFUNCTIONS