Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Can someone review my screenshot and confirm if this is a bug (pretty sure it is) and advise of any known workarounds?
I can't upload the file right now -- but the screenshot explains everything, and you can literally reproduce this with two records in a two column table.
The issue is that when you set the X axis start and end range on a Line Chart, Power BI seems to adjust it based on timezone (I'm in US EST) or some other criteria. And in this case, it causes nothing to show in the chart.
Thank you.
Solved! Go to Solution.
Hi @bvy ,
I understand your concern about the behavior of the X-axis in your Power BI line chart. Based on your description and the screenshot:
The issue you're encountering is likely related to Power BI's handling of date-time values. When you set a custom range for the X-axis, Power BI applies the UTC offset of your system time zone (in your case, US EST). This can cause a mismatch between the range you define and the actual data displayed.
For example:
Here are some solutions to resolve this issue:
Ensure that both the data and the custom X-axis range are in the same time zone (preferably UTC):
Use a calculated column to adjust the time values:
UTC_Timestamp = [YourTimestampColumn] - TIME(5,0,0) // Adjusts for US EST
Replace 5 with your time zone's UTC offset (e.g., -5 for EST without daylight savings).
Use this UTC_Timestamp for the X-axis range and the chart.
If you don't need precise time values, you can convert the timestamps to text and use them as the X-axis:
Display_Timestamp = FORMAT([YourTimestampColumn], "MM/DD/YYYY HH:MM AM/PM")
Check the Power BI report's model settings:
Instead of manually setting the start and end range, create measures for dynamic X-axis limits based on your data:
MinTimestamp = MIN('YourTable'[YourTimestampColumn]) MaxTimestamp = MAX('YourTable'[YourTimestampColumn])
Use these measures in your visual's slicer or dynamic range logic.
Sometimes Power BI's auto-scaling conflicts with custom settings. To ensure the chart displays your data:
If none of these workarounds resolve your issue, it might indeed be a bug. You can log a ticket with Microsoft support. Let me know if you'd like additional guidance.
Please mark this as solution if it helps. Appreciate Kudos.
Hi @bvy ,
This issue occurs because the x-axis range in this context only accepts dates, not times. Even if you specify the earliest timestamp for the minimum and the latest timestamp for the maximum, Power BI ignores the time component and only considers the date.
In your case, both the minimum and maximum are recognized as 11/1/2024, since Power BI focuses solely on the date range. Additionally, because your x-axis type is set to Continuous, Power BI assigns arbitrary times to the defined date range (e.g., 11/1/2024). For instance, in my dataset, I don’t even have a data point at 10:00 AM, yet Power BI displays one.
As you can see, the system expects only a date and not a datetime value:
To demonstrate, I replicated your data and made some adjustments by filling in a timestamp with different dates rather than times. As shown below, Power BI correctly recognized the defined range when working on a date level instead of a time level:
Hey thanks for taking the time to dig into this with me. What you say isn't quite true, however. The x-axis absolutely undertands the time component. My actual production app has data with 4.5 hours of continuous readings from 10AM to 2:30 PM. Power BI creates an axis from 3PM to 7:30 PM. So it MUST be looking at the available time points to create the axis. Also your screenshot covers two months -- the problem is much less apparent when viewed over very long periods. I thnk the narrative provided by @FarhanJeelani gets closer to the actual issue .
Hi @bvy
Thank you very much Bibiano_Geraldo and FarhanJeelani for your prompt reply.
Can you tell me if your problem is solved? If yes, please accept it as solution.
If you're still having problems, provide some dummy data and the desired outcome. It is best presented in the form of a table.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @bvy ,
I understand your concern about the behavior of the X-axis in your Power BI line chart. Based on your description and the screenshot:
The issue you're encountering is likely related to Power BI's handling of date-time values. When you set a custom range for the X-axis, Power BI applies the UTC offset of your system time zone (in your case, US EST). This can cause a mismatch between the range you define and the actual data displayed.
For example:
Here are some solutions to resolve this issue:
Ensure that both the data and the custom X-axis range are in the same time zone (preferably UTC):
Use a calculated column to adjust the time values:
UTC_Timestamp = [YourTimestampColumn] - TIME(5,0,0) // Adjusts for US EST
Replace 5 with your time zone's UTC offset (e.g., -5 for EST without daylight savings).
Use this UTC_Timestamp for the X-axis range and the chart.
If you don't need precise time values, you can convert the timestamps to text and use them as the X-axis:
Display_Timestamp = FORMAT([YourTimestampColumn], "MM/DD/YYYY HH:MM AM/PM")
Check the Power BI report's model settings:
Instead of manually setting the start and end range, create measures for dynamic X-axis limits based on your data:
MinTimestamp = MIN('YourTable'[YourTimestampColumn]) MaxTimestamp = MAX('YourTable'[YourTimestampColumn])
Use these measures in your visual's slicer or dynamic range logic.
Sometimes Power BI's auto-scaling conflicts with custom settings. To ensure the chart displays your data:
If none of these workarounds resolve your issue, it might indeed be a bug. You can log a ticket with Microsoft support. Let me know if you'd like additional guidance.
Please mark this as solution if it helps. Appreciate Kudos.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
96 | |
69 | |
44 | |
38 | |
29 |
User | Count |
---|---|
154 | |
93 | |
63 | |
42 | |
41 |