Forum Discussion
not a legal oleaut date - cannot refresh
- 8 years ago
Hi there,
Dit you check the actual datevalues in your table? You most probably have a date before 1/1/1900 in one of the date fields in the table you're trying to load.
Kind regards,
Hans
Just for those who got this problem also, as i did.
As stated above, i checked my data and found 1 entry with the year 0033. Once i corrected that problem, my data refreshed OK.
Anonymous wrote:Just for those who got this problem also, as i did.
As stated above, i checked my data and found 1 entry with the year 0033. Once i corrected that problem, my data refreshed OK.
This should be added as a #bug and be marked as error in PBI desktop since PBI service can't handle it.
- Anonymous7 years agoNot applicable
Maybe, but isnt the problem the underlying data rather than the app?
Zunair wrote:
Anonymous wrote:Just for those who got this problem also, as i did.
As stated above, i checked my data and found 1 entry with the year 0033. Once i corrected that problem, my data refreshed OK.
This should be added as a #bug and be marked as error in PBI desktop since PBI service can't handle it.
Maybe, but isnt it an issue with the data rather than the app?
- Zunair7 years ago
Advocate II
Sure the data has a problem, but it should be caught in the desktop app before it gets caught in pbi service. Especially since pbi desktop suppose to show the errors in the new error check chart.