漏洞
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.
| 漏洞 ID 编号 | BUG-000111200 |
|---|---|
| 已提交 | January 29, 2018 |
| 上次修改时间 | June 5, 2024 |
| 适用范围 | ArcGIS GeoEvent Server |
| 找到的版本 | 10.5 |
| 操作系统 | Windows OS |
| 操作系统版本 | 2012 R2 |
| 状态 | Known Limit |
附加信息
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)重现步骤
漏洞 ID: BUG-000111200
软件:
- ArcGIS GeoEvent Server
当漏洞状态发生变化时获得通知
发现关于本主题的更多内容
搜索相关信息
查找与此主题相关的培训
探索想法并提供反馈
获取来自 ArcGIS 专家的帮助
下载 Esri 支持应用程序