How to sync Angular Report Center with Paginated Reports (hidden UserID → cascade Enterprise)

[Bhargava_Badda]

Hi Community,

We have a web application built in Angular that includes a Report Center, where multiple Power BI Paginated Reports are going to be embedded.

When a user logs into the application, we capture their UserID. The requirement is that when a user clicks on any report in the Report Center, the report should automatically filter or cascade data (for example, Enterprise list) based on that UserID ; we also have Role ID.

Each paginated report already includes a hidden UserID parameter, and the Enterprise parameter is designed to cascade from it.

I would like to understand:

1. What are the prerequisites or best practices at the report level (inside Power BI Report Builder) to ensure the hidden parameter and cascading logic work correctly when the report is embedded?

2. From the Angular side, what’s the recommended way to pass the hidden UserID parameter — via the embed URL (rp:UserID=value) or via the parameterValues property in the embed configuration?

3. Are there any specific settings in Power BI Service or Workspace (e.g., dataset connection, RLS, permissions) that must be aligned for this setup to work smoothly?

Essentially, I’m trying to ensure the web application’s user context stays in sync with the paginated report parameters when embedding reports dynamically from a Report Center.

Any guidance, official documentation links, or reference examples would be greatly appreciated!

Thanks in advance.

[grazitti_sapna]

Hi @Bhargava_Badda 

Following are the best practices to make this work smoothly:

1. Report Builder Setup:
   • Ensure your paginated report’s UserID parameter is marked as hidden.
   • Set up cascading parameters correctly inside Power BI Report Builder—Enterprise parameter should cascade from UserID.
   • Use datasets to provide available values that respect these hierarchical parameter relationships.
2. Embedding Parameters in Angular:
   • parameterValues: [ { name: "UserID", value: userIdFromApp }, { name: "Enterprise", value: enterpriseValue }]
   • This ensures parameters are passed securely and dynamically at runtime.

3. Power BI Service/Workspace Config:

   • Confirm paginated reports and datasets have correct permissions for the app workspace.

   • If using Row-Level Security (RLS), ensure roles align with the UserID filtering logic.

   • Embed tokens generated should include the necessary permissions and parameter context if using app owns data embedding.

Also, for official documentation please check these:

• https://learn.microsoft.com/en-us/javascript/api/overview/powerbi/embed-paginated-report
• https://learn.microsoft.com/en-us/power-bi/paginated-reports/parameters/add-cascading-parameters-rep...
• https://learn.microsoft.com/en-us/javascript/api/overview/powerbi/powerbi-client-angular

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!