@krkshitij This is primarily because a Date Axis isn't configured for HeatMapChart and a String axis is fed by default to the xAxisType prop of CartesianChart

@Shubhabrata08 Yes, you are right. You can find some discussions about this issue here.

But the fix seems to be a bit more involved. Currently, a string axis is created regardless of the data type, which uses the d3 scaleBand utility. This utility has a bandwidth property that is used to determine the width and height of rectangles. The d3 scaleLinear and scaleTime utilities, used for number and date axes respectively, don't have such a property. We may need to figure out another way to resolve this issue.

@krkshitij Is there a POC or draft under review currently regarding this issue?

@Shubhabrata08 No, I haven't seen any.

@AtishayMsft I found an approach to solve this issue.
The label issue occurs only when we format data xAxisDateFormatString="%Y"
So its formatted as string in HeatMap component and then it is converted as Number in Cartesian (since cartesian component is used by other components too its not a good approach to update the cartesian component)

What we can do is whenever xAxisDateFormatString="%Y" we can add a prefix "Y " this will stop cartesian component to localise the year. below is the example

Adding prefix can remove localisation of date as number and there is no need to update cartesian component

And further if we don't want the prefix to be printed we can just remove the "Y " from cartesian component and we will get the result

This might not be the right approach. But this will not affect cartesian component.

keep open