GIT Integration issues with Paginated Reports connected with Direct Lake Semantic model

[RohanIng]

I have a Premium workspace with Git integration enabled, which is linked to an Azure DevOps repository. Everything is functioning as expected for the semantic model and Power BI reports.

However, we are encountering an issue with our Paginated reports. These reports are connected to a Direct Lake semantic model within the same workspace. When I publish these Paginated reports, they automatically appear as "Synced" rather than "Uncommitted," and I am unable to commit them to the Azure DevOps repository. Despite the Git Status indicating "Synced" in the workspace, the reports do not appear in the Azure DevOps repository.

 This issue does not occur with Paginated reports connected using import mode; it seems to be specific to reports connected via the Direct Lake semantic model.

[Anonymous]

Hi @RohanIng 

You can check if there are any specific configurations or settings in your workspace that might be affecting the Git integration for Paginated reports. 

And the document below might be helpful to understand the constraints and best practices for using Direct Lake with Paginated reports.

Learn about Direct Lake in Power BI and Microsoft Fabric - Microsoft Fabric | Microsoft Learn

Best Regards,
Community Support Team _ Ailsa Tao

[RohanIng]

Hi @Anonymous , Thank you for your response.

We have rechecked the workspace configuration and did not identify any issues. As previously mentioned, the Git Integration works correctly with other Fabric objects, including the semantic model and Power BI reports. 

It appears to function properly with Paginated Reports connected to an Import model. The only issue we’ve encountered is with Paginated Reports connected to a Direct Lake Semantic model.