To homepage To homepage
Solved

ODX error the numerical value is too large to fit into a 96 bit decimal

  • 28 March 2023
  • 3 replies
  • 99 views
christian.koeken
Rank
Badge

Dear Support,

I'm running into a weird error when I try to load customer data from the customer table of Navision. 

The error is: The numerical value is too large to fit into a 96 bit decimal.

I use a query table to only get the columns I need. In this query table I use a where clause in which I exclude some customernumbers. But now I found out that I also need these numbers in my customer dimension. But when I clear the WHERE clause, the error comes up again.

If I execute the same query in SQL Management studio it runs good and I don't see some strange values in one of the columns.

Do you have any idea?

icon

Best answer by G-T 28 March 2023, 15:09

View original

3 replies

Thomas Lind
Rank
Userlevel 6
Badge +5

Hi Christian

Do you have the source data type and the BU data type available and are they the same?

Could you try to make a specific query that reverses the where clause to get the specific rows that gives issues. You can use management studio to do this.

It would be a specific field that contains this value that is somehow too large.

G
Rank
Badge

In limited situations i have seen it where the source and target regional settings (specifically the decimal separator) are not the same, sometimes 300.2345743225 can become 3002345743225. If the ‘where’ clause is used to exclude some customer numbers as per Thomas’s idea, this will help you to get just those numbers you were excluding at first. Then it should be possible to do a try_cast() to the expected target type to see which fails.

Christian Hauggaard
Rank
Userlevel 6
Badge +5

Hi @christian.koeken did the above answers manage to resolve the issue? If so please help us by marking a best answer. Or let us know if you have any follow up questions

Reply


Terms and ConditionsCookie settings