In Deployment pipeline cycle, list of reports and deployment rule options in stages are invisible

[PriyankaHadmode]

In Deployment pipeline cycle, list of reports in stages are not appearing and deployment rule is not accessible while deploying Paginated reports. why? And in below situation, which deployment option is better suitable for this situation?  -

Where I am having PPI license & workspace is hosted on Fabric F16 capacity.

I am using oracle database as data source, so parameterized deployment approach is not working because of complex connection string. And shared dataset is also not feasible option since it is paginated report.

[PriyankaHadmode]

Thank you Menaka Kota and Poojara for response!

My colleagues who have same licensing as mine they can see list of reports under each stage but I can not. If some features are not supported then it should reflect based on licensing. How this could be the case?

[v-menakakota]

Hi @PriyankaHadmode ,

Even though paginated reports have some limitations in deployment pipelines, the visibility of items in each stage isn’t only based on licensing. Since your colleagues with the same license can see the reports, here are a few things you can check:

Please confirm whether the report you're working with is a paginated report (.rdl) or a regular Power BI report (.pbix). Only .pbix reports and semantic models are fully supported in the pipeline stage.
Ensure you're using the same workspace type as your colleagues (e.g., Fabric-backed) and that the workspace is correctly connected to the pipeline stage. Sometimes, different workspaces might be connected to different pipeline stages.
Make sure you have at least Contributor access to all pipeline stages. If your access is limited, some reports may not be visible to you.

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Best Regards, 
Menaka Kota 
Community Support Team 

[PriyankaHadmode]

Hi Menaka,

we are using same licesing, same workspace with Admin rights of Fabric capacity and deployment pipeline is also similar. List of reports are visible to them.

[v-menakakota]

Hi @PriyankaHadmode ,

If you are still unable to solve the issue you can reach out to Microsoft Support by raising a ticket with Microsoft Support. So that the backend team can investigate further using diagnostic telemetry.

Please refer below link on how to raise a contact support or support ticket. 
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn 

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Best Regards, 
Menaka Kota 
Community Support Team 

[v-menakakota]

Hi  @PriyankaHadmode ,
Thanks for reaching out to the Microsoft fabric community forum.
I would also take a moment to thank @Poojara_D12   , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference. 

Paginated reports (.rdl) are not yet fully supported in Fabric's deployment pipelines. That’s why they might not show up in the list of items at each stage, and you won’t be able to apply deployment rules like parameters or data source changes features that work for .pbix reports or semantic models. This is a known limitation, especially when using complex data sources like Oracle.

 For more details on how Fabric handles deployment between pipeline stages, I’d recommend reviewing the official documentation:

The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Best Regards, 
Menaka Kota 
Community Support Team 

[Poojara_D12]

Hi @PriyankaHadmode 

In your deployment pipeline cycle, the reason why paginated reports do not appear in the list of stage items and why deployment rules are inaccessible is due to the current limitations in Power BI’s deployment pipeline support for paginated reports. Unlike standard Power BI reports (.pbix), paginated reports (.rdl) are not fully integrated into the deployment pipeline experience—especially when it comes to applying deployment rules or viewing them alongside semantic models and reports in the UI. This is a known limitation as Microsoft continues to expand Fabric capabilities, but as of now, paginated reports require manual handling or alternative deployment strategies.

Given your situation—where you have a Power BI Premium Per User (PPI) license but your workspace is hosted on a Fabric F16 capacity, and you're using an Oracle database with a complex connection string that prevents parameterized deployment—the most suitable deployment option is manual deployment using APIs or PowerShell scripts. Since paginated reports cannot leverage shared datasets and dynamic parameterization of Oracle connection strings is not feasible, using the Power BI REST API or the New-PowerBIReport cmdlet (from Power BI PowerShell) gives you full control to upload, bind data sources, and publish to the appropriate workspace stage. This manual method allows you to handle the complexity of Oracle connections, bypassing the limitations of the deployment pipeline UI, and ensures consistent deployment to test, dev, and production workspaces.