Numéro d’ID de bogue |
BUG-000101582 |
Envoi | December 19, 2016 |
Dernière modification | August 28, 2025 |
S’applique à | ArcGIS GIS Server |
Version trouvée | 10.4.1 |
Système d’exploitation | Windows OS |
Version du système d’exploitation | 7.0 64 Bit |
Version de correction | 2.0 |
Statut | Fixed
Le bogue a été corrigé. Pour plus d’informations, reportez-vous aux sections Version de correction et Informations supplémentaires, le cas échéant.
|
Solution de contournement
Publish a map service in ArcMap from the same data and returnUpdates works as expected when new data is added.1. Create an ArcMap map document with a layer of time data from a registered SDE.2. Publish the map document as a dynamic map service to ArcGIS GIS Server.3. Execute returnUpdates REST call: time extent is correct for the current data set.4. In ArcMap, start an editing session, add a new feature with a date later than the previous time extent of the data set.5. Query the REST service, and sort by date field DESC, confirm newly added record shows up.6. Execute returnUpdates REST call again: time extent is CORRECT, i.e., the endTime value has been updated to account for the newly added feature with a later date.Service used for this test (publishing from ArcMap): <a href="https://bberry.esri.com/server/rest/services/DisastersTimeEnabledDayIntervalVideo/MapServer/0" target="_blank">https://bberry.esri.com/server/rest/services/DisastersTimeEnabledDayIntervalVideo/MapServer/0</a>
Étapes pour reproduire
ID de bogue: BUG-000101582
Logiciel: