This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 39%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Hello!
Title basically says it all.
I have a .bim file on compatibility level 1600 that I am unable to open in VS 2022 / SSDT current version and I can't seem to find a solution to make it work.
Do the current versions of VS/SSDT support editing bim files of that compatibility level?
If not, what alternative ways are there to deal with this issue? Downgrading does not appear to be an option.
Best Regards
Gerrit
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hello @Gerrit Mühe ,
Welcome to Microsoft Q&A forum. Based on my test, it seems that VS 2022 doesn’t support compatibility level 1600 currently. Installing AS extensions and SQL Server related components provided in VS Installer didn’t work(haven't tried to install SQL Server 2022). May I ask how you got this .bim file(compatibility level 1600)?
Hello @Tianyu Sun-MSFT ,
Thanks for commenting on my issue and clarifying that the current release of VS 2022 & SSDT does not yet support SSAS Tabular compatibility level 1600!
Unfortunately, I do not know myself how the raised compatibility level came to be initially! It does not appear in any commit on the .bim file for the last half year I checked. I am currently considering deleting the model off the Az-SSAS instance completely and do a fresh deploy of the latest version committed to repository as I see no other way out of this. We would be fine keeping the higher compatibility level, but that is not a viable option while VS does not support it yet.
Let me know if you have further advice on what to try / where to check for additional info!
Best Regards
Gerrit
Hi Gerrit,
I recommend double confirming this(whether VS 2022 supports SSAS tabular compatibility level 1600 now, or missing some specific extensions) by raising a ticket on our Developer Community. If it’s truly not supported currently, then I’m afraid, as upgrading the compatibility level is irreversible, you may need to wait for VS supports it.
Best Regards,
Tianyu
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 0%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETL%3C/text%3E%3C/svg%3E)
Compatability mode 1600 is garbage. Avoid at all costs or you'll be redoing a lot of work in compatability mode 1500.
It only allows you to create tables with sql queries by making an expression and promoting that to a table. Then if you ever have to edit it, guess what. Doesn't work. To get it to work you have to delete your table. Then guess what? Bye-bye measures and relationships and hidden columns and security. Idk what Microsoft was thinking with this garbage.
Oh and you also can't access the model property to roll back to compatability 1500. Great job Microsoft.