Omniscope thinks this value is an integer and automatically places thousands separator. In the Field organiser block, choose the data type Integer, and remove the separator.
After that you might wish to change this data type to Category, in case you have a limited number of repetitive values, you wish to use for filtering and further analysis.

Hi Paola,

Thanks for the rapid response. The separator is not the problem. The value itself is altered by Omniscope...

Your value might have gone over the numerical field limit, which would have caused rounding. Make sure the value is formatted as text on input, also as text in Omniscope.
To prevent Omniscope from triggering automatic number input, you could add extra 2 rows where that field value will be abc text (then remove rows later).

Hi Alexander,

You should definitely import this type of data as text. There is no need for you to store it as a number, since it is only an identifier - and as Paola stated it exceed the maximum value for a number in Omniscope.

Unfortunately there is no way to do this in the Database import block at the moment - however we will add an option to import all fields as text to resolve this problem. In the meantime you can modify the SQL statement so the data is imported as text, for example in SQL Server you might do something like:

SELECT convert(nvarchar(4000), MY_NUMBER_FIELD) FROM MY_TABLE

Thanks for the replies!

Chris, can I combine your SQL query with more fields?
SELECT field1,field2,field3, convert(nvarchar(4000, recordid) FROM MY_TABLE ?

It works! Thanks!