Bug
In ArcGIS Data Interoperability, when integrating a JavaScript Object Notation (JSON) file with 64-bit signed integer values as well as 64-bit unsigned integer numbers, the 64-bit signed integers appear correctly, but the 64-bit unsigned integers are converted to negative numbers.
| Bug ID Number | BUG-000156639 |
|---|---|
| Submitted | March 15, 2023 |
| Last Modified | May 15, 2025 |
| Applies to | ArcGIS Pro |
| Version found | 3.0.4 |
| Operating System | Windows OS |
| Operating System Version | 10.0 64 Bit |
| Status | Known Limit |
Additional Information
The geodatabase has a known range limit of -2 ^ 53 minus 1 and 2 ^ 53 minus 1. While the Workbench app can read big integer values up to 2 ^ 64, the values cannot be written in the geodatabase as destination formats due to these known limits. Refer to this documentation https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/arcgis-field-data-types.htm#ESRI_SECTION2_8BF2454C879941258DC44AF6BB31F386 for more information.Workaround
If the user wants to keep the values from the source format to the geodatabase, the workaround is to convert the big integer values to string.Steps to Reproduce
Bug ID: BUG-000156639
Software:
- ArcGIS Pro
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App