cancel
Showing results for 
Search instead for 
Did you mean: 

Invalid OADate value - Datetime2 decimal accuracy - 9999-12-31T23:59:59.9999999

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?

Status: Needs Info
Comments
Community Support Team

Hi @Barslund ,

 

When did you get this error? Loading the dataset or making data transformation? Could you please share the PBIX file containing dummy data so that I can reproduce? Besides, here is a similar thread for your reference, please check if it similar to your scenario.

 

Best regards,

Yuliana Gu

Community Support Team
Status changed to: Needs Info
 
Member

@v-yulgu-msft 
Only when visualising the data, as in putting the datetime2 column directly into the visualization - table for example.

 

Data is pulled in Direct Query mode, so hard to replicate with dummy data.

 

Server is SQL 2016.