Report usage metric

[Peter_23]

Hi communiy! . I have a report usage metric, which I development based on another model (A), so I'm trying to deploy from devel to test enviroment, but it's unsupported, where is its SM?, I didn't find...

If I have to read the metrics from SM (A) in Prod enviroment, how to link to new enviroment? If its not deployment..

I mean I have to create a new report in prod enviroment?? 😐

Thanks in advance.

[Peter_23]

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 😞

[v-saisrao-msft · Accepted solution]

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. 

[rohit1991]

Hi @Peter_23

It looks like your usage metrics report is built on top of a dataset (Model A) from another workspace or environment, which is causing the "Unsupported" status during deployment.

This usually happens when the report is linked to a model that doesn’t exist or isn’t properly referenced in the target environment. To fix it, either:

• Repoint the report in Production to the correct version of Model A, or

• Deploy Model A to Production first, then reconnect your report to it.

In some cases, you may need to manually rebuild or rebind the report if automatic linking isn’t supported.

[Akash_Varuna]

Hi @Peter_23 The issue arises because the report is linked to the semantic model in development, which doesn’t automatically connect in production.

To fix this, re-link the report in production to the production semantic model. Ensure the semantic models are aligned across environments, and use Deployment Rules in the pipeline to map the correct model.