Forum Discussion
Developing Embedded Reports Setup
Hello everyone!
I'm new to PowerBI and am looking for some guidance on a couple things related to embedded.
Our setup: We basically have a front end web application that connects to a database server where each customers database is stored. We are going to be adding embedded reports so the customers can dig around in the reports us developers create within the app. Since our customers each have their own database, I'm going to assume it is best to create a workspace for each one which means over 100 workspaces. The schema that the reports will be looking at are the same across all databases.
For report developers - what's the preferred way to create a report and get it to all of these workspaces? Is there some way where one report can handle the many and just pass in a parameter that tells it to go look at this or that customer? Or are we going to have to push out a report to each workspace which means updating them will be a lot of work (100+ times).
What will the report developer need to prep for when developing such a report?
Sorry if this is a general question but all of my searching and reading up on this has me confused and I hope someone can help me understand or point me to some resources that I may have missed.
Thank you.
2 Replies
Hi, letsgobro ;
You can check if these related post can is useful to you.
https://www.youtube.com/watch?v=5OF0s2t0N3w
Best Regards,
Community Support Team_ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.I've done some more investigating and have come to the following conclusions:
- In our case, it will be best to have a workspace for each customer since they each have their own database.
- Create a single workspace that will hold the reusable report that all customers will access.
- Create a dataset for each customer that will dynamically bind to said report. This is a lot of maintenance but don't see any way around it.
- Nothing special is needed in the report and the dynamic binding is all done on the application side of the house.
If I'm mistaken on anything I mentioned above, please let me know.
