We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hello,
I have database1
| Labor | Job | Part | No Part | Length |
| Ara | A21 | Body | 1 | 200 |
| Ara | A21 | Body | 2 | 200 |
| Ara | A21 | Head | 2 | 150 |
| Kiano | A21 | Head | 1 | 300 |
| Kiano | A21 | Body | 2 | 200 |
| Kiano | A21 | Body | 3 | 400 |
| Edi | A21 | Body | 3 | 400 |
| Edi | A21 | Body | 4 | 180 |
| Fahri | B25 | Head | 1 | 200 |
| Fahri | B25 | Body | 1 | 250 |
| Fahri | B25 | Head | 2 | 350 |
| Kiano | B25 | Head | 2 | 350 |
| Kiano | B25 | Head | 3 | 100 |
And database2
| Inspector | Labor | Job | Part | No Part | Length | Result | Defect |
| Dino | Ara | A21 | Body | 1 | 200 | ACC | - |
| Dino | Ara;Kiano | A21 | Body | 2 | 200 | Repair | Crack;Oversize |
| Dino | Ara | A21 | Head | 2 | 150 | ACC | - |
| Dino | Kiano | A21 | Head | 1 | 300 | Repair | Underfill |
| Dino | Kiano;Edi | A21 | Body | 3 | 400 | ACC | - |
| Dino | Edi | A21 | Body | 4 | 180 | ACC | - |
| Mario | Fahri | B25 | Head | 1 | 200 | Repair | Undersize;Spatter |
| Mario | Fahri | B25 | Body | 1 | 250 | ACC | - |
| Mario | Fahri;Kiano | B25 | Head | 2 | 350 | Repair | Crack |
| Mario | Kiano | B25 | Head | 3 | 100 | ACC | - |
I want to connect that two databases. I make:
1. a slicer for Labor (from database1)
2. a pie chart for Result (from database2)
3. a card for Length (from database2)
I want when I choose 'Ara' from slicer, then a pie chart and card can show the result for Ara.
and, I want Length can sum value like this:
| Dino | Ara;Kiano | A21 | Body | 2 | 200 | Repair | Crack;Oversize |
in this row, there are two labor for executing part Body No 2 Job A21, so Ara's length 100 and Kiano 100.
How to do it? Can anyone help me? Thank you in advance.
Hi @ffirda99
I would suggest you to go through some basics of table relationships with design basis of dimensional modelling.
Then you can go through how to create relationships in tables:
https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-create-and-manage-relationships
But before crreating relationship directly, you may need to transform your tables either in source or in Power query. This shall be done once you understand the design needs for your tables based on above research.
Hope it helps.
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 |
|---|---|
| 57 | |
| 38 | |
| 33 | |
| 19 | |
| 16 |
| User | Count |
|---|---|
| 68 | |
| 66 | |
| 41 | |
| 34 | |
| 25 |