Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Score big with last-minute savings on the final tickets to FabCon Vienna. Secure your discount

Reply
Anonymous
Not applicable

Cannot convert column value to custom column and set type to time

Hi all,

 

 I have what appears to be unix epoch time in ms (I think). I tried creating a custom column with 

#datetime(1970, 1, 1, 0, 0, 0) + #duration(0, 0, 0, [UnixTime]/1000)

however that does not work and results in Error values

 

If I use this instead

#datetime(1970, 1, 1, 0, 0, 0) + #duration(0, 0, 0, 1410907851)

 

I do get results but are the same date and time in 2014. What am I missing here?

 

 

2 REPLIES 2
v-juanli-msft
Community Support
Community Support

Hi @Anonymous 

#duration(0, 0, 0, 1410907851) means 1410907851 seconds,  when you add 1410907851 seconds to the date 1970/1/1, it will get 2014 by default.

 

Please show me which result do you want, i can test and find the solution for you.

 

Best Regards
Maggie

 

Community Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Anonymous
Not applicable

@Maggie  @v-juanli-msft  I think this format is actually in epoch ms time but for some reason this resulted in an error when I applied it.

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.

Top Solution Authors