Supplies are limited. Contact info@espc.tech right away to save your spot before the conference sells out.
Get your discountScore big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount
I prepated a semanatic model ( sm_coursereg) in PBI desktop.
In that , I also created a table ( report file , sm_coursereg.pbix ) and created a cluster . This added a calculated measure in my model.
From this one semantic model , I have generated multiple reports with no issues.
And when I try use the cluster in another report ( let us say cluster.pbix ) based on "coursereg" semantic model , I am getting an error as shown.
Also , the report ( sm_coursereg.pbix ) works fine in the PBI desktop and the same report in PBI service throws an error as shown.
Solved! Go to Solution.
Hi @zahirmohideen,
Based on your scenario, I understand that the error occurs after a subsequent data refresh. Since reprocessing the semantic model worked initially but failed after the second data refresh, it indicates that the issue might be related to the data refresh.
Check the data refresh logs and schema changes. If the underlying schema of the data source has been modified such as column names, data types, or table structures, it could cause the model to break. Validate data consistency, especially around the Mailing Zip Code column. Ensure this column is populated correctly, and check for nulls, incorrect values, or invalid formats.
Additionally, validate the relationships in your model and check for any missing or broken relationships that could be causing issues. If any relationships are invalid, they can break the model and cause errors during refresh, Ensure there are no missing or broken relationships between tables, especially if clusters relies on certain tables being joined. Also try to reprocess the model to fix any invalid states that might have occurred after the data refresh. Look for errors like missing data, data type mismatches, or data truncation that might be contributing to the failure.
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,
Anjan Kumar Chippa
Hi @zahirmohideen
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Hi @zahirmohideen ,
We wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Regards,
Hi @zahirmohideen ,
We wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
If our response addressed, please mark it as Accept as solution and click Yes if you found it helpful.
Thanks and regards,
Chaithra E.
I reprocessed semantic model . It worked fine for one day .
After the 2nd day ( another data refresh) , it produced the same error
Hi @zahirmohideen,
Based on your scenario, I understand that the error occurs after a subsequent data refresh. Since reprocessing the semantic model worked initially but failed after the second data refresh, it indicates that the issue might be related to the data refresh.
Check the data refresh logs and schema changes. If the underlying schema of the data source has been modified such as column names, data types, or table structures, it could cause the model to break. Validate data consistency, especially around the Mailing Zip Code column. Ensure this column is populated correctly, and check for nulls, incorrect values, or invalid formats.
Additionally, validate the relationships in your model and check for any missing or broken relationships that could be causing issues. If any relationships are invalid, they can break the model and cause errors during refresh, Ensure there are no missing or broken relationships between tables, especially if clusters relies on certain tables being joined. Also try to reprocess the model to fix any invalid states that might have occurred after the data refresh. Look for errors like missing data, data type mismatches, or data truncation that might be contributing to the failure.
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,
Anjan Kumar Chippa
Hi @zahirmohideen,
Thank you for reaching out to Microsoft Fabric Community.
Thank you @Deku for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the super user resolved your issue? or let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Thanks and regards,
Anjan Kumar Chippa
If not in a valid state you may have to process the semantic model.
Reprocessing every day is not a viable option .
User | Count |
---|---|
32 | |
17 | |
11 | |
9 | |
8 |
User | Count |
---|---|
51 | |
31 | |
25 | |
17 | |
15 |