Forum Discussion

Anonymous

Not applicable

4 years ago

Recent change in X-axis behaviour to continuous axis for categorical chart

Hi, I have just obsereved on the power bi report service that I am no longer be able to show continous x axis if I am using a legend field. This used to work before (until last week) , here...

Need Help

Anonymous

Not applicable

4 years ago

Hi Aniya,

Here I will be using the "Retail Analysis Sample" PBIX file.

After downloading the file, opening it, creating a new page, I make a Line Chart view with:

X Axis: Store -> "OpenDate" as a date hierarchy,

Y-Axis: Sales -> "Average Unit Price"

Legend: Item -> "Category"

I then drill down, "expand all", to the lowest level of data. This is what it looks like in desktop:

Notice the X-Axis is continuous:

Then I publish the report. This is what it looks like in the service:

Notice the X-Axis is now categorical, and broken. There is no way to change it back in the service.

This is a bug, please look to resolve. I will look to make a separete post about this also.

Cheers,

jareynolds

Regular Visitor

4 years ago

I am able to replicate the same issue Anonymous is experiencing in Power BI Desktop after installing the September 2022 release. It seems to be a (hopefully) unintended side effect of the recent change to hierarchical x-axis behavior.

As others have stated, the issue appears to occur when using a Line visual with a built-in Date hierarchy on the x-axis, and only when a legend is applied.

Using the same visual setup as the above example, also from Retail Analysis Sample:

X-axis is Continuous by default when set to OpenDate (non-hierarchical)

When the x-axis is changed to use the built-in date hierarchy for OpenDate, the hierarchy is now fully expanded by default, but the x-axis is now Categorical and the Continuous x-axis is no longer available.
Prior to the September update, the default behavior was a Continuous x-axis when the built-in date hierarchy was fully expanded, but it is now Categorical and cannot be changed.

JustSayJoe
Advocate IV
3 years ago
I just ran into this same issue today, and it looks like nobody from Microsoft has resolved it yet... awesome. Anybody find a work around in the past few months?