Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi,
Can anyone help with creating a bell curve (will be used in a stacked area chart) for workload planning?
My columns:
projectID | startDate | endDate | noOfItems | days
The idea is to have something like the screenshot below, but I can't get the values to be correct.
I've been trying to make it work for the last few days and I'm slowly losing my mind. Thanks in advance! 🙂
EDIT: I've managed to sort it out, I think I just needed a rest as I was staring at it for too long. Thanks!! 🙂
Solution:
When I was originally trying to do it I was doing it in DAX (calculated table) and couldn’t really pinpoint what was going wrong – the pattern was fine, but the values were not matching – sum of items per day was not equal the actual item number. The values were super small – 0.01 etc. or 3x the actual values. After having a weekend off (I was still thinking about it but not really looking at it) I've decided to do it in Power Query, step by step to have more control over it. Maybe not ideal for some people, but that's what worked for me, our database is not big at all.
Step by step:
Number.Exp(-(([Day Number] - [Mean]) * ([Day Number] - [Mean])) / (2 * [StdDev] * [StdDev]))
SUMX(
'TableName',
'TableName'[NormalisedWorkloadPercentage] * 'TableName'[noOfItems]
)
And it worked.
Solved! Go to Solution.
Solution:
When I was originally trying to do it I was doing it in DAX (calculated table) and couldn’t really pinpoint what was going wrong – the pattern was fine, but the values were not matching – sum of items per day was not equal the actual item number. The values were super small – 0.01 etc. or 3x the actual values. After having a weekend off (I was still thinking about it but not really looking at it) I've decided to do it in Power Query, step by step to have more control over it. Maybe not ideal for some people, but that's what worked for me, our database is not big at all.
Step by step:
Number.Exp(-(([Day Number] - [Mean]) * ([Day Number] - [Mean])) / (2 * [StdDev] * [StdDev]))
SUMX(
'TableName',
'TableName'[NormalisedWorkloadPercentage] * 'TableName'[noOfItems]
)
And it worked.
Hi @sheyyka
It looks as if you have solved the problem yourself.
Could you please share your solution here when time permits? This will benefit other users who are experiencing the same problem.
Thank you in advance for your time and dedication.
Best Regards,
Jarvis Tang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Solution:
When I was originally trying to do it I was doing it in DAX (calculated table) and couldn’t really pinpoint what was going wrong – the pattern was fine, but the values were not matching – sum of items per day was not equal the actual item number. The values were super small – 0.01 etc. or 3x the actual values. After having a weekend off (I was still thinking about it but not really looking at it) I've decided to do it in Power Query, step by step to have more control over it. Maybe not ideal for some people, but that's what worked for me, our database is not big at all.
Step by step:
Number.Exp(-(([Day Number] - [Mean]) * ([Day Number] - [Mean])) / (2 * [StdDev] * [StdDev]))
SUMX(
'TableName',
'TableName'[NormalisedWorkloadPercentage] * 'TableName'[noOfItems]
)
And it worked.
Yeah sure, the is the data roughly:
We need your data to do anything .....
Phil
Proud to be a Super User!
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
78 | |
78 | |
57 | |
37 | |
34 |
User | Count |
---|---|
99 | |
56 | |
56 | |
46 | |
40 |