The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I need support to migrate RDL files from SSRS 2019 version (reports available in SSRS) to power BI and i need to edit the datasource as AWS on rds postgre SQL. Anyone please support on this also the gateways part
Solved! Go to Solution.
Hi @Varadha123,
Thanks for reaching out to the Microsoft fabric community forum.
Here's how you can approach the migration and setup:
* To migrate RDL to Power BI you can use Power BI Report Builder to open your existing .rdl files created in SSRS 2019. Review and modify the reports as needed to ensure compatibility. Power BI supports paginated reports, and these can be published to the Power BI Service if you have a Premium workspace (either PPU or capacity-based). After opening the .rdl in Report Builder, go to File > Save As and publish it directly to your Power BI workspace.
* Now update data source to AWS RDS PostgreSQL. In Report Builder, go to Data Sources, edit the existing connection string, and change it to point to your AWS RDS PostgreSQL instance. Example of connection string format "Host=your-db-endpoint.amazonaws.com;Port=5432;Database=your-db-name;Username=your-username;Password=your-password;". Make sure the credentials and database are accessible from the network where the gateway will be hosted.
* Then set up On-premises data gateway. Since Power BI Service doesn’t directly connect to RDS PostgreSQL without a gateway, you’ll need to install an on-premises data gateway (standard mode) on a machine that can reach the RDS endpoint. After installing, sign in with your Power BI account and configure the gateway from Power BI Service (Manage Gateways). Add a new data source under the gateway: choose PostgreSQL as the connector and enter the same details you used in the RDL.
* Now bind Gateway data source to the Report. In Power BI Service, go to your paginated report’s settings and map it to the configured gateway and data source. This step will ensure the report can refresh and run using the RDS PostgreSQL connection through the gateway.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
Hi @Varadha123,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If so, it would be really helpful for the community if you could mark the answer that helped you the most. If you're still looking for guidance, feel free to give us an update, we’re here for you.
Best Regards,
Hammad.
Hi @Varadha123,
To clarify your follow-up question "Do the Gateway and Power BI Report Builder credentials need to be the same?", No they don’t have to be the same. In Report Builder, the credentials are used locally to connect and test the report before publishing. In Power BI Service, the gateway data source needs its own credentials (these are stored securely in the cloud and used during report execution).
So, you can use different credentials in each place, but make sure the credentials set up in the gateway have access to the same PostgreSQL database and permissions required to run the queries.
Here are few Microsoft article that covers the full process of publishing paginated reports to Power BI, including gateway setup:
MS Learn - Create a paginated report from a Power BI report or dataset
Also check this for gateway setup and PostgreSQL connectivity:
Power Query PostgreSQL connector - Power Query | Microsoft Learn
Guidance for deploying a data gateway for the Power BI service - Power BI | Microsoft Learn
Best Regards,
Hammad.
One more clarification I want integrate the power bi service to Aws .
The ssrs reports( rdl) which was published is power bi service they want restrict the access based on the user how can we do it?
Do we have any option in power bi service itself for rdl reports?
Hi @Varadha123 ,
Migrating SSRS (RDL) reports from SSRS 2019 into Power BI is a common request, but there are some things to keep in mind:
Steps in short:
If you get stuck on any step (import, data source config, or gateway), feel free to ask with specifics!
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
translation and formatting supported by AI
Hi @Varadha123,
Thanks for reaching out to the Microsoft fabric community forum.
Here's how you can approach the migration and setup:
* To migrate RDL to Power BI you can use Power BI Report Builder to open your existing .rdl files created in SSRS 2019. Review and modify the reports as needed to ensure compatibility. Power BI supports paginated reports, and these can be published to the Power BI Service if you have a Premium workspace (either PPU or capacity-based). After opening the .rdl in Report Builder, go to File > Save As and publish it directly to your Power BI workspace.
* Now update data source to AWS RDS PostgreSQL. In Report Builder, go to Data Sources, edit the existing connection string, and change it to point to your AWS RDS PostgreSQL instance. Example of connection string format "Host=your-db-endpoint.amazonaws.com;Port=5432;Database=your-db-name;Username=your-username;Password=your-password;". Make sure the credentials and database are accessible from the network where the gateway will be hosted.
* Then set up On-premises data gateway. Since Power BI Service doesn’t directly connect to RDS PostgreSQL without a gateway, you’ll need to install an on-premises data gateway (standard mode) on a machine that can reach the RDS endpoint. After installing, sign in with your Power BI account and configure the gateway from Power BI Service (Manage Gateways). Add a new data source under the gateway: choose PostgreSQL as the connector and enter the same details you used in the RDL.
* Now bind Gateway data source to the Report. In Power BI Service, go to your paginated report’s settings and map it to the configured gateway and data source. This step will ensure the report can refresh and run using the RDS PostgreSQL connection through the gateway.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
Hi Hammad/Burrak,
Thank you for your clarification...
Few more clarification..
1. Gateway and Power Bi report builder Credentials should be same?(Username and password)
Can you suggest me any article which have the entire steps?
Adding a point am using paginated report to publish it in power Bi service
Hi @Varadha123,
To clarify your follow-up question "Do the Gateway and Power BI Report Builder credentials need to be the same?", No they don’t have to be the same. In Report Builder, the credentials are used locally to connect and test the report before publishing. In Power BI Service, the gateway data source needs its own credentials (these are stored securely in the cloud and used during report execution).
So, you can use different credentials in each place, but make sure the credentials set up in the gateway have access to the same PostgreSQL database and permissions required to run the queries.
Here are few Microsoft article that covers the full process of publishing paginated reports to Power BI, including gateway setup:
MS Learn - Create a paginated report from a Power BI report or dataset
Also check this for gateway setup and PostgreSQL connectivity:
Power Query PostgreSQL connector - Power Query | Microsoft Learn
Guidance for deploying a data gateway for the Power BI service - Power BI | Microsoft Learn
Best Regards,
Hammad.
Hi @Varadha123,
I wanted to quickly follow up on your issue. Was your issue resolved in the end?
If yes, it’d be great if you could share a quick update and accept a solution, so other users can benefit from your experience too.
If you’re still stuck, let us know, we’re more than happy to continue helping you through it.
Best Regards,
Hammad.
Hi @Varadha123l,
We noticed there hasn’t been any recent activity on this thread. If your issue is resolved, marking the correct reply as a solution would be a big help to other community members.
If you still need support, just reply here and we’ll pick it up from where we left off.
Best Regards,
Hammad.
One more clarification I want integrate the power bi service to Aws .
The ssrs reports( rdl) which was published is power bi service they want restrict the access based on the user how can we do it?
Do we have any option in power bi service itself for rdl reports?
This is little urgent could u pls support
Hi @Varadha123,
Based on your description, you're publishing SSRS (.rdl) reports to Power BI Service and looking to restrict access based on users especially in an embedded setup tied to AWS.
Here are a few points that can help you with
* Once RDL (paginated) reports are published to Power BI Service (typically in a Premium workspace), access is governed at the workspace level or through app permissions if the report is shared via an app. There's currently no built-in row-level security (RLS) for paginated reports like you have in regular Power BI datasets. Access control is binary which means either the user can access the report or not.
* You can have user based access restriction. If your reports need to show different data based on who is viewing (like RLS), you’ll have to parameterize your report. You can pass user-specific parameters (like user ID, department, etc.) into the RDL report via the URL or API and handle data filtering within the report query itself (e.g., using WHERE conditions in SQL).
* In an embedded scenario, you'll likely be using App Owns Data model. You can generate embed tokens per user, and include report parameter values in the embedding logic. This way, each user sees only what they're allowed to. But remember, you must enforce this security in the data source layer (e.g., SQL views that filter based on passed parameters), since Power BI won't handle it for RDL.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Using embedded
Hi @Varadha123,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If so, it would be really helpful for the community if you could mark the answer that helped you the most. If you're still looking for guidance, feel free to give us an update, we’re here for you.
Best Regards,
Hammad.