Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi,
I'm using system versioned SQL tables, and I'm getting an error that I'm not sure if it's intentional or a bug.
In trying to visualize a [datetime](7) column, where I'm getting this:
"
Couldn't load the date for this visual
Invalid OADate value '2958466'. Accepted values are between -657435.0 and 2958465.9999999
"
The value I'm trying to visualize is 9999-12-31T23:59:59.9999999, which would be the standard max value for a T-SQL [datetime2](7) column.
As a note, I can see that Power BI will accept a [datetime2](2) column with the value of 9999-12-31T23:59:59.9900000.
Any explanation as to why Power BI will not accept this standard [datetime2](7) value, but requires fewer decimals / accuracy to render?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.