How to fix Comapatibility level error , when trying to create Analysis Services Tabular project created using Tabular editor. Same error using VS 2022 and 2026. Please advise.
-
Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator
Hi DNR,
I hope you had a chance to review the information shared earlier, and I hope this information has been helpful! If you still have questions, please let us know what is needed in the comments so the question can be answered.
-
DNR 0 Reputation points
Hi Manoj,
Thank you for sharing that. Looks like compatibility error is gone, but still not able to load .bim file through VS 2022/2026.
Thank you.
-
Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator
Hi DNR,
This indicates that the .bim model contains Power Query (M)–based data sources (Mashup queries). Models that include M partitions are supported only by Power BI / Fabric semantic model engines, and cannot be loaded into Visual Studio’s local Analysis Services workspace or deployed directly to SSAS/Azure Analysis Services.
the file you’re opening is structured as a Power BI semantic model, not a native SSAS/AAS tabular project, which is why Visual Studio is unable to load it.
You have two supported paths depending on your goal:
Option 1: Keep it as a Power BI / Fabric model (recommended if you need Power Query transformations) Continue working with this model using Power BI Desktop, Tabular Editor, or XMLA endpoint connections to a Premium/Fabric workspace. Visual Studio is not required for this scenario.
Option 2: Convert it to an SSAS/AAS-compatible model If your intention is to open or deploy the model through Visual Studio or SSAS/AAS, the M-based partitions must be removed and replaced with supported data source partitions (for example SQL queries or structured sources). This can be done in Tabular Editor by editing each table partition and replacing the M expression. After removing all Mashup/M sources, the model can be opened in Visual Studio.
Hope this helps, Please let us know if you have any questions and concerns.
-
Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator
Hi DNR,
Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.
Sign in to comment
1 answer
-
Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator
Hi DNR,
The error you’re seeing:
“The operation cannot be performed because it references an object or property that is unavailable in the current edition of the server or the compatibility level of the database.”
is caused by a compatibility level mismatch between your tabular model and the Analysis Services engine being used to host the workspace database.
When you open a Tabular project in Visual Studio, the model is deployed to a local workspace instance of the Analysis Services engine. If the model was created in Tabular Editor using a newer compatibility level (for example 1600, which targets SQL Server 2022 / Power BI engine), and the workspace engine or Azure Analysis Services supports only up to compatibility level 1500, the deployment fails with exactly this error.
Azure Analysis Services supports compatibility level 1500. Compatibility level 1600 and higher are supported in SQL Server 2022 Analysis Services and Power BI / Fabric semantic models, but not in Azure Analysis Services. If your model was created using Power BI defaults or SQL 2022 settings, that is likely the cause.
To resolve this, open the model in Tabular Editor and check the CompatibilityLevel property. If it is set to 1600 (or higher), change it to 1500, save the model, and reopen it in Visual Studio. Also make sure the Visual Studio project’s Target Server Version is set to Azure Analysis Services or SQL Server 2019, and that the compatibility level matches 1500. If the model uses features introduced in 1600 (for example certain metadata properties or Power BI–specific features), those must be removed before lowering the compatibility level.
Also ensure your Visual Studio Analysis Services extension is up to date, because the workspace engine version is tied to the installed designer components.
Helpful Reference:
https://learn.microsoft.com/en-us/analysis-services/tabular-models/compatibility-level-for-tabular-models-in-analysis-services?view=sql-analysis-services-2025Hope this helps, Please let us know if you have any questions and concerns.