invantive documentation
Invantive Support ForumsLog In / Sign Up

Itgenxml091 in the BARCODE field

Replies happen on the forum.

Go to source

Question

During the synchronisation of Items to Exact Online, we receive the following error:

itgenxml091 The ‘BARCODE’ column has a value ‘10788942212008112505’, which cannot be converted to the Int64 data type. The value ‘10788942212008112505’ is not a valid large integer. The value was either too large or too small for an Int64. Please use a comma ‘,’ as the separator for thousands.

Request ID: 0HNN7G8UUIJP0:00000001

As a result, synchronisation fails.

Could you please investigate why the BARCODE field is treated as an Int64 rather than as text (string)?

Accepted answer

A fix has been deployed to resolve this issue. Five columns have been removed due to the transition from XML to REST tables.

For further information, see:

Invantive Cloud release frequency

forums.invantive.com

Reply 8

This question was automatically closed after 1 week of inactivity. The last answer provided has been marked as the solution.

Please ask a new question in a separate thread if the problem reoccurs. Please include a link to this thread in the new question by pasting its URL into the text.

Reply 2

956b2b1d2d1bcc4efe1a7108bd7a177224ec2851

itgenxml091

The column BARCODE in Items has a value ‘10788942212008112505’ which cannot be converted to the ‘int64’ data type.

The value ‘10788942212008112505’ is not a valid large integer. The value was either too large or too small for an Int64.

Please use a comma ‘,’ as the separator for thousands.

Reply 3

This is because the data type used for this field in the Invantive software allows for a value that is too large. A change will be made to resolve this issue.

Report: gmr-eol-items

Call stack:

System.OverflowException
ValidationException
ValidationException
   at System.Number.ThrowOverflowException[TInteger]()
   at System.String.System.IConvertible.ToInt64(IFormatProvider provider)
   at Invantive.Data.DataUtility.ConvertToLong(GlobalState owner, ExecutionOptions executionOptions, Object val)

SQL statement:

select /*+ result_set_name('Items') */
       ...
,      itm.barcode
       ...
from   ( select to_number(itm.division_code) division
         ,      to_guid(replace(itm.id_attr, '{', '', '}', '')) id
         ,      itm.*
         from   exactonlinexml..items@eol itm
       ) itm
...

Exact Online specifies in the metadata that it is an integer:

<xsd:element name="Barcode" type="xsd:integer" minOccurs="0"/>

The largest possible input value in the Exact Online user interface itself is 20 nine nines:

99999999999999999999

The number 10788942212008112505 has 20 digits and exceeds the maximum value of 19 digits for an Int64 (9223372036854775807).

Within the REST APIs, Exact Online uses a text value rather than an Int64, as is the case with XML. A text value is also preferable because of the potential leading zeros.

Reply on the forum