Hi, Our SQL Server business datastore table keys are setup as BIGINT

chrisc834 over 9 years ago

Hi,

Our SQL Server business datastore table keys are setup as BIGINT datatypes. The 'Defining Custom Data Types' article below states that BIGINT is supported and to map using xsd:long type in CDT's:

forum.appian.com/.../Defining_a_Custom_Data_Type.html

We have implemented on this recommendation, however it appears the native Appian 'Number(Integer)' datatype cannot handle numbers bigger than the standard INTEGER range?

For example, when querying a datastoreentity and the key is 110523001, results are returned but when using the key 20275908001 no results are returned, even though a row exists in the table.

Please help, thanks

Discussion posts and replies are publicly visible

Parents

0 PhilB
A Score Level 1
over 9 years ago

Where did you see the decimal types being turned into scientific notation? That can happen when entering data into a floating point field (frankly I think it's a bug) but it's possible to handle those larger decimal numbers in text fields by wrapping the value and the save in a todecimal() function.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 PhilB
A Score Level 1
over 9 years ago

Where did you see the decimal types being turned into scientific notation? That can happen when entering data into a floating point field (frankly I think it's a bug) but it's possible to handle those larger decimal numbers in text fields by wrapping the value and the save in a todecimal() function.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data