Bug
Unable to update features based upon the TRACK_ID field in GeoEvent definition if the case does not match the field in the feature service.
| Bug ID Number | BUG-000111200 |
|---|---|
| Submitted | January 29, 2018 |
| Last Modified | June 5, 2024 |
| Applies to | ArcGIS GeoEvent Server |
| Version found | 10.5 |
| Operating System | Windows OS |
| Operating System Version | 2012 R2 |
| Status | Known Limit |
Additional Information
When a feature service is published – whether that be from ArcMap, Pro, GeoEvent Server, or an admin API – the service is the final arbiter of what it will and will not accept. There may be limits placed on the length of strings, or limits on which fields are “nullable”. The most obvious limit tends to be the structure / schema of the attribute fields and the field names. GeoEvent Server will allow you to create a GeoEvent Definition whose event fields are mixed case, and it will allow you to use that event definition to publish a feature service. The geodatabase’s RDBMS may force the feature class / table to use all upper-case or all lower-case field names – that’s just how it handles the external server’s request. Any discrepancies are part of the published map/feature service’s spec which establishes the contract any client or external server must honor when making requests on the service. The recommended best practice is to use a Field Mapper to guarantee the event structure / schema exactly matches that of the feature service in which they want to add or update feature records. Refer to the blog 'Understanding GeoEvent Definitions' (https://community.esri.com/community/gis/enterprise-gis/geoevent/blog/2015/06/05/understanding-geoevent-definitions)Steps to Reproduce
Bug ID: BUG-000111200
Software:
- ArcGIS GeoEvent Server
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