Forum Discussion
Dataflows date and import issues
Hi jcullum ,
Locale property is used to help power bi to recognize record values that diff from your device region format, it does not mean the display format. (e.g your date value stored as 'UK' date format but your system region is 'US', you can modify locale to 'UK' to help recognize 'UK' date values)
For data column type recognize issues, you can enter to query editor and manually fixed this in 'change type' step.
In fact, this optional parameter will include when you use on desktop side. (it will auto-generated based on the corresponding connector) It seems like power bi dev team forgot to add these parts on the dataflow side. (you can contact them and report this issue)
Regards,
Xiaoxin Sheng
Hi Xiaoxin,
So i managed to fix the dd/mm/yyyy display issue. In-case someone else comes across the same problem, it was a language setting in Chrome, I needed to specifically add the English (Australia) language and make sure it was at the top of the list and set to "This language is used to display the Google Chrome UI". Interestingly i could not get Edge to work either.
The other problems still exist, i am just waiting for some in my organisation to assist with ticket.
Thanks for your help on the display issue.
Same issue now for two months.
MS team are aware that non-US dates do not load correctly in dataflows, but as of today's advice have kicked the "fix" back to February.
Where the data source comes from SharePoint, even more issues are created due to the US date format default - but even explicitly setting the date to AU region will not resolve the error.
Latest suggested resolution was to leave all date fields as text....