Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Instead of slopes between datapoints in a graph, I would like to visualize only horizontal and vertical straight lines. To achieve this, I used a lag function to add a fake datapoint one second in time before every real datapoint, with the value of the real datapoint that came at the last datapoint before it. By doing this, the idea is that every slope is contained within 1 second, making it invisible on a plot for multiple weeks.
The problem I encountered is that when visualising this data, it seams that PowerBI randomly ignores some of the fake datapoints when the time window is increased. The result of this behaviour is that there are slopes visible.
Example:
real data x: [10s, 20s, 35s, 60s]
real data y: [0,2,4,2]
new data x: [9s, 10s, 19s, 20s, 34s, 35s, 59s, 60s]
new data y: [0,0, 0, 2, 2, 4, 4, 2] (I just copied the first datapoint to create its fake predecessor to maintain equal column lengths)
To make it a bit more clear, this is what I want to happen:
And you would expect the fake data added with the lag function would achieve this, but this is not the case. PowerBI could for example ignore the value at x=34s, resulting in a sloped line between x=20s and x=35s.
I know the 'stepped' option allows only straight lines, but this does not solve the issue: using stepped in this case would make it seem like the value increases right in between x=20s and x=35s, while the increase should be visualised where it actually happens: at x=35s.
Is there anyone that could help me solve this issue?
Solved! Go to Solution.
For anyone with the same issue stumbling across this post: the problem in this case turned out to be PowerBI's high-density sampling: https://docs.microsoft.com/nl-nl/power-bi/create-reports/desktop-high-density-sampling Follow the instructions on this page to disable it and enable more precise data representation.
For anyone with the same issue stumbling across this post: the problem in this case turned out to be PowerBI's high-density sampling: https://docs.microsoft.com/nl-nl/power-bi/create-reports/desktop-high-density-sampling Follow the instructions on this page to disable it and enable more precise data representation.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 55 | |
| 48 | |
| 38 | |
| 16 | |
| 15 |
| User | Count |
|---|---|
| 83 | |
| 71 | |
| 38 | |
| 28 | |
| 25 |