Forum Discussion
Idea for Waterfall Chart
Hi,
I have 2 tables, the first with the transport orders and their respective planning date (theoretical)
and the second with the history of the transport order status on 01/27 and 01/28.
For example, the status of the order c1 is Executed - Actual Day on the day 27/01 (it was executed that day) and on the 28/01 it remains with that status but with the indication "Last Day" to show that it was executed at an earlier date. Another example is the c10 transport order that is not executed on 01/27 due to a machine failure and then 01/28 is executed.
My idea is to show through a waterfall chart as a step from the number of transport orders planned for a specific day to the transport orders that are actually scheduled that day and in the end to what was actually executed that day, the scheme is the following:
I have seen some examples of how to make a waterfall graph in power bi but they were generally applied to a single table and with a single measure, and I think in this case I have to create several measures but I have no idea where to start.
I'm not sure if the way the information displayed in the second table is the most appropriate, I would appreciate an idea of how to make it more efficient.
I appreciate your support, thanks
2 Replies
- v-lili6-msft
Community Support
hi apcor
To my knowledge, it could not achieve in waterfall chart for now, you could only drag one measure into Values of this visual.
Maybe you could just use table visual or matrix visual for your requirement.
Regards,
Lin
- apcorFrequent Visitor
Hi Lin,
I made one last attempt to make the waterfall graph, I did this:
I built the following table:
Then I created a measure that assigns the values I want to each "Factor-Component" pair to create the waterfall graph:
So far so good, check that the assigned values are correct, the problem is that when I want to create the waterfall graph I get this error:
What I want to achieve is something like the figure below, I did this by copying the values to another table in a new power bi file to check if the error came from the table structure:
Thanks for the support, I really appreciate it
Regards
Anthony