不具合
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 Support アプリのダウンロード