This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
I am building a paginated report that is displaying project statuses with task sub-statuses (in a many to one relationship). The source data is coming from a Power BI dataset source. In report builder, I create two datasets to get the project and task rows into two separate tables. My first question is do I need to structure the data like this versus a single table with the fields merged?
My more important question is when it comes to putting the project fields in a rectangle to mimic a status PowerPoint slide (it's final exported destination), when I place a table with task fields within the rectangle, I receive the error "Tablix has a detail member with inner members, Detail member can only contain status inner members". When I move the task table below the rectangle, all the tasks are displayed after all of the projects.
What is the proper way to display (parent/child) items in a many to one relationship on a single page? Thanks!
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
| User | Count |
|---|---|
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |