Forum Discussion
Report Build & Distribution Architecture
I am a new user of PowerBI and have some questions about recommended tech stacks for a given report workflow I am conceptualizing. Not knowing the full range of the PBI service, I would appreciate some recommendations and/or established practices for similar scenarios.
SCENARIO:
Using a PowerBI semantic model as a data source, automate report build and distribution of individual paginated reports that are filtered off a customer UID.
CURRENT METHOD:
Report Design:
- Power BI report builder
- Source: PBI semantic model
- Parameter for Customer UID
Report Distribution:
- Power Automate
- Use PBI connector to pull all Customer UIDs into a list variable
- Loop through list
- Using PBI connector, export the paginated report with the current Customer UID passed as a report parameter.
I would love to receive your feedback and/or recommendations on other methods. Thank you!
2 Replies
Hi goodbyetonto ,
According to your statement, I think you requirement is to restrict data based on User ID.
Here I suggest you to set up row level security in your report. Dynamic RLS may be a good way to achieve your goal.
For reference:Row-level security (RLS) with Power BI - Microsoft Fabric | Microsoft Learn
Set up row-level security in Power BI paginated reports - Power BI | Microsoft LearnSample:
Dynamic Row Level Security with Power BI Made Simple - RADACAD
Best Regards,
Rico ZhouIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Rico Thank you, although this is not what I was soliciting for information on. Being new to the Power Platform, and to Power BI specifically, I wanted to ask this audience for feedback with my approach to report builds and distributions using Power Automate. I provided specs in my message as to how I planned to pass in a param when building and exporting and was hoping to hear from anyone who has approached this common scenario differently and has had consistent results. Thank you for your reply!
