Forum Discussion
Super UserWe couldn't parse the input provided as a Date value.
Fixed, it was locale issue. If someone need to know more about this or need help, please send me an email at [email protected].
thanks,
P
Memorable MemberDo a sort on that column A-Z and Z-A to see if you have any extreme outlier value like year 5000 or something.
Right now that is all I can think of for the cannot parse type message.
You could do a sanity check and make a duplicate of the column with a different name and see if that will upload into Service okay.
Super UserFixed, it was locale issue. If someone need to know more about this or need help, please send me an email at [email protected].
thanks,
P
- CahabaData
It would be best if you post a generic description of your fix as someone could search this topic a year from now and never find out how to resolve.
- parry2k
Great Idea and here is the solution.
Locale on powerbi desktop was set to Canada means date value dd/mm/yyyy and in my dataset the date was dd/mm/yyyy so everything was working fine in desktop
But when I published, i was getting the parsing error and here was the fix:
- change locale in powerbi desktop to USA means mm/dd/yyyy format and after I made this change I started same parsing error in PowerBI Desktop
-To resolve this I changed the value of my date column in google sheet to match with locale mm/dd/yyyy
- this worked fine in desktop and once published to powerbi service there was no error.
In nutshell it seems like PowerBI Service expect date mm/dd/yyyy format until there is a way to change locale in powerbi service.
I hope this is helpful.
Thanks,
Parv
- CahabaData
Thank you for posting the fix; I do believe it all is manageable - it may depend on your Service domain.....not sure if domain is the correct Microsoft term... essentially where it is hosted... although possibly when you originally initiated Service it may have asked, and/or you can alter in the Power BI Admin area... Others are more versed in managing PBI Service than myself so I don't have this fix at my finger tips - - but the user base is very international - - but fundamentally it does make sense that one must align the format end to end.....