Odata with UNIX date in column headers creating error upon refresh

[DBNN]

Hi All,

I have a powerBI file that searches its content via Odata.  All nice but for some reason the Odata column names sometimes contain UNIX date values ie: ABC_1577750400.   And these collumns are used in filters in my PBI file.  No problem but as soon as I want to refresh the next day I get an error on all my visuals saying he does not find the date.    I have a workaround for it with each times renaming to the old date after refresh but it looses me lots of time every day.   Is there an easy way to solve this?

Many thanks, 

[v-yingjl]

Hi @DBNN ,

Could you please consider sharing the detail error message in visuals when you refresh the data source for further discussion?

Best Regards,
Community Support Team _ Yingjie Li

[DBNN]

Hi, Below the screenshot of the error.  Odata adds a UNIX datevalue after the titles of my columns (some columns) and I need to rename that in my query because it looks stupid on a visual in the end.  The next day refresh, then the refresh stalls because it does not recognize the renamed column.

My workaround is, remove the renaming in query editor, refresh, save , rename in power query to the first UNIX code date when the file was made (I saved this one), then rename the visual  then save.

Sounds stupid but its the only thing that seems to work for now.  Hope you can help

[v-yingjl]

Hi @DBNN ,

After you rename it, have you close and apply it in power query?

If applies but still not works, you could try to publish a copy of this pbix file after Disable the "Auto Date/Time" option for it. Please test it with an extra copy of your pbix file.

If it still has the same issue, perhaps the best workaround may be like your mentioned before, although it would be complex.

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

[DBNN]

Thanks for the help but it does not seem to help.  When I refresh the query it blocks and tells me that column with the UNIX date is not found.    Am back to my workaround 🙂