Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register 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!
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |