Forum Discussion
Using Cluster in PBI Service throws an error
- 1 year ago
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
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