Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago
Solved

Table showing blank rows when using HH:MM:SS time format issue

Hello,

 

I have a table in which I display all my relavant business data and until now I was displaying my different time-related values in simply total seconds. However, once values get too large and there are several minutes worth of seconds, it is not so easy to read so I changed my time format to HH:MM:SS (or whatever HH:NN:SS is in Power BI)

 

The issue I am having is that after making that change and when filtering the data using slicers, the table now shows empty rows with persistent 00:00:00 values in the columns with time values. For example, if I filter my data because i only want to see January's data then instead of the table just displaying January as it always did before, now it does what you see below. Where the dates not currently selected in the slicer are blank except for the 00:00:00 values in the time-related columns.

 

Date# of orders# of items in orderavg call lengthavg time customer waitedship dateship type
february  00:00:0000:00:00  
february  00:00:0000:00:00  
january3200:07:1900:03:10jan 312 day
january5700:21:0300:02:19jan 30normal
january1300:11:3100:02:47jan 29next day
december  00:00:0000:00:00  
november  00:00:0000:00:00  
november  00:00:0000:00:00  
november  00:00:0000:00:00  

 

Does anyone know how to fix this or what could possibly be going on here? I appreciate any assistance. This is a really inconvenienet bug and I cannot seem to fix it on my end.

 

EDIT: Because my original seconds value is not a date/time format value, the way i created the HH:MM:SS value is by using the TIME function. So I have a measure that does the following calculation...

 

Time_Format_Fixed = TIME(0,0,[Total_Time])

 

Thank you ahead of time.

  • Anonymous's avatar
    Anonymous
    4 years ago

    Believe it or not, i just found the issue and I'm smacking my head agaisnt the wall because of it lol

     

    While i correctly created a Date column in my data table to then make the relationship to the calendar table... i used that date column from my data table instead of the date from the calendar table.

     

    I just switched table's date field to be the one from the calendar table and the bug is gone.

     

    While the fix was dumb, i believe that is something Power BI should be able to handle better.