Forum Discussion
Helper IScorecards not refreshing when underlying models are refreshed via Data factory
Hi dpollozhani ,
At the moment, Fabric Data Factory pipelines are designed primarily for orchestrating semantic model refresh execution, but they do not explicitly guarantee downstream event propagation to dependent artifacts such as Scorecards.
In contrast, refreshes triggered via manual actions or the REST API operate within an event-driven framework that Scorecards rely on to detect updates.
As a result, even though the semantic model refresh completes successfully when triggered through a pipeline, the “refresh completed” event that Scorecards depend on may not be emitted in the same way. This explains the observed behavior where manual or API-triggered refreshes update Scorecards correctly, while pipeline-triggered refreshes do not.
As a workaround, you can adopt a hybrid approach by continuing to use pipelines for orchestration while adding a final step that triggers a REST API refresh for datasets used by Scorecards. Even a lightweight follow up API refresh can help ensure that the necessary event signal is generated, allowing Scorecards to update as expected.
Thank you.
Community SupportHi dpollozhani ,
At the moment, Fabric Data Factory pipelines are designed primarily for orchestrating semantic model refresh execution, but they do not explicitly guarantee downstream event propagation to dependent artifacts such as Scorecards.
In contrast, refreshes triggered via manual actions or the REST API operate within an event-driven framework that Scorecards rely on to detect updates.
As a result, even though the semantic model refresh completes successfully when triggered through a pipeline, the “refresh completed” event that Scorecards depend on may not be emitted in the same way. This explains the observed behavior where manual or API-triggered refreshes update Scorecards correctly, while pipeline-triggered refreshes do not.
As a workaround, you can adopt a hybrid approach by continuing to use pipelines for orchestration while adding a final step that triggers a REST API refresh for datasets used by Scorecards. Even a lightweight follow up API refresh can help ensure that the necessary event signal is generated, allowing Scorecards to update as expected.
Thank you.
Helper IThank you for your answer.
I'll go ahead an trigger a notebook that calls a "Calculate" refresh type via the REST API on my model within the same pipeline, but I hope that this becomes native functionality soon.