Forum Discussion
Report usage metric
- 1 year ago
Hi Peter_23,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Thank you rohit1991, Akash_Varuna for your helpful in insights.
The issue you're encountering arises because the report is connected to a semantic model that exists only within the Development environment. At present, deployment pipelines do not support deploying reports that reference semantic models which are not included in the pipeline or mapped via deployment rules.
The approach you are following is correct:
- First, deploy the semantic model (Model A) to the Testing environment.
- Then, create a new version of the report in Testing and connect it to the deployed semantic model.
Since re-linking a report to a dataset across environments is not currently supported within deployment pipelines, your decision to recreate the report in the target environment is the appropriate solution.
If this resolves your issue, please consider marking your reply as the accepted solution so it can assist other community members facing the same scenario.
Thank you.
Thanks rohit1991 Akash_Varuna I have to deploy the SM to test enviroment ok, but the report usage metric is still in devel ... 😔 so I didn't find the option to re-link to the SM (test enviroment).
I figure out to create a new report usage metric 😞
Hi Peter_23,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Thank you rohit1991, Akash_Varuna for your helpful in insights.
The issue you're encountering arises because the report is connected to a semantic model that exists only within the Development environment. At present, deployment pipelines do not support deploying reports that reference semantic models which are not included in the pipeline or mapped via deployment rules.
The approach you are following is correct:
- First, deploy the semantic model (Model A) to the Testing environment.
- Then, create a new version of the report in Testing and connect it to the deployed semantic model.
Since re-linking a report to a dataset across environments is not currently supported within deployment pipelines, your decision to recreate the report in the target environment is the appropriate solution.
If this resolves your issue, please consider marking your reply as the accepted solution so it can assist other community members facing the same scenario.
Thank you.