Forum Discussion
Duplicating Nodes/Label Question: Sankey 3.4.3
So! I want to have a diagram that shows two flows [eachs, spend] over three cycles [Current, Proposed, Actual], with each node being a physical item that my company has/will spent money on.
I am almost there, I would create bookmarks so that there is a view for the different flows [you see the eaches or spend only].
I get the idea that for each row, a node is created like Source -> Target and the Weight is the width of the node. My problem is that when the source node name is the [Item Name] it creates two flows from one node. I would prefer it to duplicate the node kind of like how it is in the documentation of the visual. That at least would give me a workaround. How would you achieve a result like the pictured image?
BASE TABLE
BrandItemCurrent.EachesProposed.EachesActual.EachesCurrent.SpendProposed.SpendActual.Spend
| Medtronic | 1234 | 10 | 10 | 10 | 10 | 10 | 10 |
| Medtronic | 123 | 20 | 20 | 20 | 20 | 20 | 20 |
| Medtronic | 12 | 30 | 30 | 30 | 30 | 30 | 30 |
| Schedtronic | 13 | 40 | 40 | 40 | 40 | 40 | 40 |
| Schedtronic | 14 | 50 | 50 | 50 | 50 | 50 | 50 |
| Schedtronic | 15 | 60 | 60 | 60 | 60 | 60 | 60 |
Transformed Table [Headers have been unpivoted and associated with the item, threw in a index label]
SOURCETARGETVALUELABEL
| 1234Current Eaches | TOTALPROPOSEDEACHS | 50 | 3 |
| 1234Proposed Eaches | TOTALACTUAL EACHS | 0 | 5 |
| 1234Actual Eaches | TOTALACTUAL EACHS | 40 | 1 |
| 1234Current Spend | TOTAL PROPOSED SPEND | 100 | 4 |
| 1234Proposed Spend | TOTALACTUALSPEND | 0 | 6 |
| 1234Actual Spend | TOTALACTUALSPEND | 40 | 2 |
| 123Current Eaches | TOTALPROPOSEDEACHS | 30 | 9 |
| 123Proposed Eaches | TOTALACTUAL EACHS | 0 | 11 |
| 123Actual Eaches | TOTALACTUAL EACHS | 20 | 7 |
| 123Current Spend | TOTAL PROPOSED SPEND | 20 | 10 |
| 123Proposed Spend | TOTALACTUALSPEND | 0 | 12 |
| 123Actual Spend | TOTALACTUALSPEND | 20 | 8 |
| 12Current Eaches | TOTALPROPOSEDEACHS | 20 | 15 |
| 12Proposed Eaches | TOTALACTUAL EACHS | 0 | 17 |
| 12Actual Eaches | TOTALACTUAL EACHS | 30 | 13 |
| 12Current Spend | TOTAL PROPOSED SPEND | 70 | 16 |
| 12Proposed Spend | TOTALACTUALSPEND | 0 | 18 |
| 12Actual Spend | TOTALACTUALSPEND | 30 | 14 |
| 13Current Eaches | TOTALPROPOSEDEACHS | 0 | 21 |
| 13Proposed Eaches | TOTALACTUAL EACHS | 50 | 23 |
| 13Actual Eaches | TOTALACTUAL EACHS | 60 | 19 |
| 13Current Spend | TOTAL PROPOSED SPEND | 0 | 22 |
| 13Proposed Spend | TOTALACTUALSPEND | 100 | 24 |
| 13Actual Spend | TOTALACTUALSPEND | 60 | 20 |
| 14Current Eaches | TOTALPROPOSEDEACHS | 0 | 27 |
| 14Proposed Eaches | TOTALACTUAL EACHS | 30 | 29 |
| 14Actual Eaches | TOTALACTUAL EACHS | 80 | 25 |
| 14Current Spend | TOTAL PROPOSED SPEND | 0 | 28 |
| 14Proposed Spend | TOTALACTUALSPEND | 20 | 30 |
| 14Actual Spend | TOTALACTUALSPEND | 80 | 26 |
| 15Current Eaches | TOTALPROPOSEDEACHS | 0 | 33 |
| 15Proposed Eaches | TOTALACTUAL EACHS | 20 | 35 |
| 15Actual Eaches | TOTALACTUAL EACHS | 70 | 31 |
| 15Current Spend | TOTAL PROPOSED SPEND | 0 | 34 |
| 15Proposed Spend | TOTALACTUALSPEND | 70 | 36 |
| 15Actual Spend | TOTALACTUALSPEND | 70 | 32 |
Hi ctho222 - Sankey diagrams require distinct node names to avoid multiple edges originating from the same “collapsed” node when conceptually they should be split.
below documentation helps you :
Multi-Level Sankey diagram in Power BI using DAX | Sankey Chart Custom Visual
Deneb: Declarative Visualization in Power BI | Deneb
Hope the above links helps.
3 Replies
- rajendraongole1
Super User
Hi ctho222 - Sankey diagrams require distinct node names to avoid multiple edges originating from the same “collapsed” node when conceptually they should be split.
below documentation helps you :
Multi-Level Sankey diagram in Power BI using DAX | Sankey Chart Custom Visual
Deneb: Declarative Visualization in Power BI | Deneb
Hope the above links helps.
