Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I am using the March 2025 release (latest) of Power BI Desktop, with the TMDL view option enabled.
I have a model with a Power Query generated calendar table that I want to copy to another report. I copy the TMDL script to the clipboard. As a test, I create a new blank report, then paste the script to the TMDL view and apply.
Then I get the error : "The database compatibility level of 1550 is below the minimal compatability level of 1567 needed for [model 'Model'].[table 'Period'].[column ''].[ChangedProperty '0'] at PowerBI mode."
Since I am using the latest version of Power BI Desktop, I would expect the db compatibility level (CL) to be to the highest level.
Yet, with TE2, I can see that it is indeed 1550. Though I can change the CL to 1567 with TE2, this beats the purpose of providing a simple way to citizen developers for including a standard calendar table in their models.
Q : Is there a way with Power BI Desktop only to raise the CL to 1567 ?
After changing the CL to 1567 with TE2, I can apply the script, but this time the error changes:
"Model validation failed. The following tables contain unsupported partitions: Period (Partition Type: M)"
But this second error does not occur if a Power Query query already exists in the model.
Alltogether, the user experience in this case is far from satisfactory, but the feature is still in preview. I am hoping this post will contribute to make it better.
Solved! Go to Solution.
FYI, I finally found solutions to both of the issues:
With that, applying the TMDL script - which was obtained from another model - works without issue.
FYI, I finally found solutions to both of the issues:
With that, applying the TMDL script - which was obtained from another model - works without issue.
Hi @bdarbo78 ,
Thank you for reaching out to Microsoft Fabric Community.
I understand that you're using TMDL to create a calendar table in your Power BI model, but you're getting an error related to partitions. Specifically, the error mentions "M" as an unsupported partition type. it seems that all partitions have a source type "m" in the JSON file, which is not a recognizable partition source type in Power BI. The most common types of partition sources are SQL, Oracle, Text/CSV, and Web.
You can try:
1. Modify the partition source type in the JSON file to a recognized partition source type.
2. Check the model.bim file for corruption.
3. Try deleting and recreating the partition in Power BI.
4.Try creating a new Power BI report and importing the model into it.
Also, make sure that you have followed the correct steps to modify and compile the pbit file using pbi-tools. Double-check that the modified JSON file is saved correctly and that the pbit file is compiled correctly.
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Thanks and regards,
Chaithra E
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
72 | |
68 | |
53 | |
39 | |
33 |
User | Count |
---|---|
70 | |
63 | |
57 | |
49 | |
46 |