Forum Discussion
13 digit EPOCH getting error when adding new column
| EPOCH COLUMN |
| 1669749375000 |
PowerBiPro2000 That's a reference to the step before the current step. You can just add a column and paste in this part of the formula:
#datetime(1970, 1, 1, 0, 0, 0) + #duration(0, 0, 0, [EPOCH COLUMN]/1000))
6 Replies
You don't need to include the table name. In fact, by using MyTable[EPOCH COLUMN] it is converting that to a list, then you are dividing a list by 1000.
Get rid of the MyTable designation. Is the data in this table? If not, you need to merge it in. You cannot reference data in other tables the same way you can DAX.
As for the formula, see Working with Unix Epoch Time In Power BI — ehansalytics - I am not sure you need the 1000 divisorPowerBiPro2000 Oh, sorry, PQ, then this:
= Table.AddColumn(#"Changed Type", "Custom", each #datetime(1970, 1, 1, 0, 0, 0) + #duration(0, 0, 0, [EPOCH COLUMN]/1000))You don't use table references in PQ
Greg_Deckler As expected, it was my error! However, now I am getting this error: Expression.Error: The name 'Changed Type' wasn't recognized. Make sure it's spelled correctly.
What am I doing wrong? Thank you for your help!
PowerBiPro2000 That's a reference to the step before the current step. You can just add a column and paste in this part of the formula:
#datetime(1970, 1, 1, 0, 0, 0) + #duration(0, 0, 0, [EPOCH COLUMN]/1000))
Greg_Deckler What does the "Changed Type" represent? I can't get past "Expression.Error: The name 'Changed Type' wasn't recognized. Make sure it's spelled correctly" I'm surprised how difficult it is to convert Epoch dates (at least it has been for me).
