Forum Discussion
Not a legal OleAut date..
Hi,
I had almost the same issue with an ODBC connection to a Progress Database. Everything works fine in Power BI Desktop but was not able to refresh once uploaded to a group.
I've applied the following work around and it works for me:
1. Go to the query designer
2. Transform the Date field(s) to a number field
3. Add another step in the Query editor
4. Set the number field back to the desired Date field.
Now i'm able to schedule and run the refresh.
I am also receiving this error - Not a legal OleAut date.. - with scheduled refresh only (on-demand refresh works fine).
mravestein - Can you please clarify the steps that you describe?
I went into desktop Power BI and changed the data type using the dropdown depicted below.
Number options were: Decimal Number, Fixed Decimal Number, Whole Number - I tried a few different ones.
My field is actually date/time so I I changed it back to that.
a) Am I making the changes in the correct place
b) Which numeric data type should I choose
c) I am not clear what you mean by step #3 (Add another step in the Query editor)
I'm new to Power BI so I appreciate any assistance you can offer.
Hi, Plysko,
By step #3 I ment, an additional step in Power BI (for example rename a column).
If you change a type, and then change it again, PowerBI only applies the last action.
for example:
Column value = 3/3/2016
If I change the type to whole number, it will be something like 21345674 (its quite random to me)If I then change the type back to date the column looks good to me, but I still get the error. Power BI ignores the change to Whole Number
I did:
Change type to "whole number"
Renamed a column
Change type to "date"
This fixed my error.
See below for the applied steps (Type gewijzigd = Changed Type in the Dutch language)