Forum Discussion
Direct lake Semantic model changed, but recognized as a new model in the deployment pipeline
Hi Anonymous,
As previously mentioned, please use the link provided in my last post to raise a support ticket.
Thank you for using Microsoft Community Forum.
Community SupportHi Anonymous,
After reviewing the details you provided, I have identified few alternative workarounds that may help resolve the issue. Please follow these steps:
The ModelID annotation is crucial for tracking dataset versions. If the ModelID differs between the test and production versions, Power BI may consider them as distinct datasets. Please ensure the ModelID is identical in both versions.
Even if the metadata in Tabular Editor matches, the dataset may have a different internal Dataset ID in the Power BI Service. To confirm, go to the Power BI Service, navigate to your workspace, and compare the dataset GUID/ID under Settings > Dataset.
If any modifications were made to table structures, relationships, or calculated columns, Power BI might recognize it as a distinct model. Instead of manually updating metadata, consider deploying the dataset using Tabular Editor’s "Save to Power BI Service" feature. Make sure to select the correct dataset during deployment.
Check if the deployment pipeline settings allow dataset updates rather than creating a new dataset. If other methods are unsuccessful, you may use Power BI’s Update Data source API to directly push the metadata update.
Kindly refer to the below following link for more information:
The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
I hope this could resolve your issue, if you need any further assistance, feel free to reach out.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.
Hi v-kpoloju-msft ,
Thanks for your response.
1. I can't see the model ID anotation in the master data tab with tabular editor, do you have a screenshot to show where I can find it?
2. Regarding "Even if the metadata in Tabular Editor matches, the dataset may have a different internal Dataset ID in the Power BI Service. To confirm, go to the Power BI Service, navigate to your workspace, and compare the dataset GUID/ID under Settings > Dataset." Isn't it every dataset has its own GUID?
3. Regarding "If any modifications were made to table structures, relationships, or calculated columns, Power BI might recognize it as a distinct model." But these opreations are normall actions we will do to change the current model, right? Why it will be recognized as a new version?
Thanks.
Best Regards.
Tiger
- v-kpoloju-msft
Hi Anonymous,
I apologize for any inconvenience caused. After reviewing the details you provided, I have outlined the following steps. Please follow the steps below:
Tabular Editor does not display the Model ID (Dataset GUID) directly because this identifier is assigned by the Power BI Service and is not stored within the Tabular Object Model (TOM) metadata that Tabular Editor accesses. To locate the Model ID (Dataset ID): Access Power BI Service, navigate to your workspace. Select the dataset and click on Settings. In the URL in your browser, the dataset ID (GUID) will be part of the URL.
Yes, each dataset in Power BI Service possesses a distinct GUID (Globally Unique Identifier). The complication arises when a dataset is altered or republished. In these instances, even if the metadata (including dataset name, tables, and columns) appears identical in tools like Tabular Editor, the internal Dataset ID (GUID) in Power BI Service may change.
Yes, modifying tables, relationships, or calculated columns is expected, but Power BI may recognize it as a new model if the dataset is republished incorrectly, structural changes alter the internal model ID, or XMLA tools track it differently. To prevent this, always publish updates to the same workspace and dataset, and verify the dataset ID in Power BI Service before and after changes.
If the issue persists, please consider raising a Microsoft support ticket. You can create one using the following link:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.Hi kpoloju,
Thanks for your explanation, then I understand what you mentioned of the GUID at the beggining. When we re-publish the dataset to the test workspace, the guid may changed due to metadata change, that will cause this issue.
But how can we fix this now? Do you have any suggestions for this? Or we can only submit a ticket to Microsoft?
Thanks a lot for your help.
Best Regards.
Tiger
- v-kpoloju-msft
Hi Anonymous,
As previously mentioned, please use the link provided in my last post to raise a support ticket.
Thank you for using Microsoft Community Forum.Thanks for your information, I will submit the ticket.