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:
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?
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?
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.
#PaginateReports #Embedding
#Power BI Embedded, #Paginated Reports, #Angular, #Parameters, User Context
