Forum Discussion
How to pass parameters from Angular to a Power BI Paginated Report (embedded in web app)?
Hi team,
We’ve developed a web application in Angular where users log in with their application credentials. Within the app, there’s a Report Center section that displays all available Paginated Reports hosted in Power BI / Fabric.
Each user in the application has a unique UserID, and our paginated reports include a hidden parameter called UserID. This parameter is used to filter and cascade report data (for example, limiting data to a specific enterprise).
We’d like to automatically pass the UserID from Angular to the report when a user selects a report from the Report Center.
Could you please help clarify the following points:
What’s the recommended approach to pass parameters (like UserID) from an Angular app to a paginated report during embedding?
Are there any report-level configurations required (such as parameter naming conventions, visibility, or default settings)?
Is it advisable to append parameters to the embedUrl (for example, &rp:UserID=1234), or is there a more robust API-based method to achieve this?
Any sample implementation or reference documentation would be greatly appreciated.
Thanks in advance!
Hi Revanth_B,
Thank you for your inquiry on the Microsoft Fabric Community Forum.
Based on my understanding, you can securely pass the UserID from your Angular application to an embedded Power BI paginated report. Please follow the approach outlined below, which may help resolve the issue.
- Generate the embed information on the server side (for example, embedUrl and a short lived embedToken) using the Power BI REST API (Generate Token / Reports - GenerateTokenInGroup). Perform this operation from your backend using either the App‑owns‑data or User‑owns‑data flow.
- Return the embedUrl and embedToken to the Angular client, ensuring that no secrets are exposed.
- Embed the report using the Power BI JavaScript API and set the parameters via parameterValues in IPaginatedReportLoadConfiguration. For example: parameterValues: [{ name: 'UserID', values: ['1234'] }].
This is an API driven and secure method. Avoid placing sensitive identifiers in public URLs in production.
For report level configuration, ensure that the parameter name exactly matches the RDL parameter (case‑sensitive). Use Hidden (not Internal) for parameters that you set programmatically, as Hidden parameters can be set by the API. If a parameter is required, ensure either a default is provided or a value is always passed to avoid rendering errors.
If your paginated report uses SSO enabled data sources or a dataset with RLS, include datasource identities or identity blobs when generating the embed token on the server side so that RLS is enforced.
Please refer to the links below for further information:
Embed Token - Generate Token - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Embed Token - Reports GenerateTokenInGroup - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Embed a paginated report in Power BI embedded analytics | Microsoft Learn
Pass a report parameter within a URL for a Power BI paginated report - Power BI | Microsoft Learn
URL parameters in paginated reports in Power BI - Power BI | Microsoft Learn
Use row-level security when embedding paginated reports - Power BI | Microsoft Learn
Embed paginated reports in your embedded analytics app - Power BI | Microsoft Learn
How to embed Power BI content in an Angular app | Microsoft Learn
IPaginatedReportLoadConfiguration interface | Microsoft LearnWe hope this information helps to resolve your issue. If you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
3 Replies
v-pnaroju-msftCommunity Support
Hi Revanth_B,
Thank you for your inquiry on the Microsoft Fabric Community Forum.
Based on my understanding, you can securely pass the UserID from your Angular application to an embedded Power BI paginated report. Please follow the approach outlined below, which may help resolve the issue.
- Generate the embed information on the server side (for example, embedUrl and a short lived embedToken) using the Power BI REST API (Generate Token / Reports - GenerateTokenInGroup). Perform this operation from your backend using either the App‑owns‑data or User‑owns‑data flow.
- Return the embedUrl and embedToken to the Angular client, ensuring that no secrets are exposed.
- Embed the report using the Power BI JavaScript API and set the parameters via parameterValues in IPaginatedReportLoadConfiguration. For example: parameterValues: [{ name: 'UserID', values: ['1234'] }].
This is an API driven and secure method. Avoid placing sensitive identifiers in public URLs in production.
For report level configuration, ensure that the parameter name exactly matches the RDL parameter (case‑sensitive). Use Hidden (not Internal) for parameters that you set programmatically, as Hidden parameters can be set by the API. If a parameter is required, ensure either a default is provided or a value is always passed to avoid rendering errors.
If your paginated report uses SSO enabled data sources or a dataset with RLS, include datasource identities or identity blobs when generating the embed token on the server side so that RLS is enforced.
Please refer to the links below for further information:
Embed Token - Generate Token - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Embed Token - Reports GenerateTokenInGroup - REST API (Power BI Power BI REST APIs) | Microsoft Learn
Embed a paginated report in Power BI embedded analytics | Microsoft Learn
Pass a report parameter within a URL for a Power BI paginated report - Power BI | Microsoft Learn
URL parameters in paginated reports in Power BI - Power BI | Microsoft Learn
Use row-level security when embedding paginated reports - Power BI | Microsoft Learn
Embed paginated reports in your embedded analytics app - Power BI | Microsoft Learn
How to embed Power BI content in an Angular app | Microsoft Learn
IPaginatedReportLoadConfiguration interface | Microsoft LearnWe hope this information helps to resolve your issue. If you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
- v-pnaroju-msft
Hi Revanth_B,
We would like to follow up and see whether the details we shared have resolved your problem. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.
Thank you. - v-pnaroju-msft
Hi Revanth_B,
We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.
Thank you.