Forum Discussion

ChrisR22's avatar
ChrisR22
Icon for Helper III rankHelper III
3 years ago

X-axis not changing with date slicer

Hello,

 

I have a chart that uses measures for count, and this is plotted over time. The time is from a calendar table. I have a between date slicer for this page, and for some reason my x axis is not being adjusted when I manipulate the slicer dates, only the data points shown change.

https://community.fabric.microsoft.com/t5/Desktop/Date-filter-does-not-update-x-axis-when-using-date-hierarchy/td-p/2361961

 

This thread makes me think it is because I have a +0 piece added at the end of my measure so that zero values would show as such instead of null, which was advice I received from this thread:

https://community.fabric.microsoft.com/t5/Desktop/show-items-with-no-data-as-0-instead-of-blanks/m-p/113165#M47732

 

However, that first thread didn't really give advice on how to remedy my situation without removing the +0, which I need to have so that null values will show as 0. 

 

Currently my measure formula looks like this:

Completed Project Volume = CALCULATE(COUNT('DataTable'[Project ID]),USERELATIONSHIP('DataTable'[Completion Date],'Calendar'[Date]))+0
 
Unless someone has another way to make null values appear as 0, does anyone know of a workaround for the axis-slicer issue?
 
Thanks so much!
 

3 Replies

  • parry2k thanks, however this example is a bit too generic for my use. I am not counting sales volume, which would be a sum of values in a 'Sales' column of a table. In my case, I am counting how many projects were completed (divided by 3 project types). Each of these projects would be counted based on count (Distinct) of Project IDs in cases where a completion date is present. Each project type would have its own 'FirstSale' and 'LastSale' so to speak. I have not been able to figure out how to work that generic example into a solution to my problem. Do you have any thoughts yourself of how you may approach this?

  • ChrisR22 exactly, that is a generic solution that should work in most of the cases. The point is to find out the first and last date, in your case it could be completely different but the logic is going to be the same.

     

    It is very hard to tell any solution without looking at your model/measure and how you are visualizing it.