You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have deployed a Tabular Model developed in Visual Studio 2019 or 2022 with the DevOps Azure Analysis Services extension.
The name of the model is set in the project properties, but when the deployed model is accessed from Power BI after deployment, the set name is ignored and the name is always "Model".
DevOps deployment tasks created in 2022 will not have this phenomenon. What could be the cause? I contacted MS and was told that this feature is an extension and cannot be supported.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
We are experiencing the same issue. The database name is correct, however, the model name is set to the default of 'Model' regardless of the model name provided in Visual Studio and committed to the the DevOps repo. Power BI dashboards connected on the dev instance would not work if connected to the prod instance since the model name is not similar. Could the model name option been added to the release pipeline in any way?
There is a deprecated option for model name, however, following the note I would expect the model name to be in line with the database name, but this is not the case.
I have deployed a Tabular Model developed in Visual Studio 2019 or 2022 with the DevOps Azure Analysis Services extension.
The name of the model is set in the project properties, but when the deployed model is accessed from Power BI after deployment, the set name is ignored and the name is always "Model".
DevOps deployment tasks created in 2022 will not have this phenomenon. What could be the cause? I contacted MS and was told that this feature is an extension and cannot be supported.
The text was updated successfully, but these errors were encountered: