BUG-000169701 for ArcGIS Online

Bug ID Number	BUG-000169701
Submitted	August 2, 2024
Last Modified	March 27, 2025
Applies to	ArcGIS Online
Version found	Feb 2024
Operating System	N/A
Operating System Version	N/A
Status	As Designed

Additional Information

To properly utilize the fieldsToCompare feature in the extractChanges function, there are important configuration steps and considerations: Configuration Requirement: Before enabling either sync or change tracking, you must set syncRowsMovedOutsideFilter on the service. This is crucial for the proper functioning of fieldsToCompare. UpdateDefinition JSON: The configuration should be set using the following JSON: {"syncRowsMovedOutsideFilter": true} Risk of Data Loss: If syncRowsMovedOutsideFilter is not enabled from the beginning, disabling sync and change tracking later can result in the loss of all previous records. This is particularly important if you need to access historical data. Current Limitation: Due to cost considerations, the fieldsToCompare feature currently only works when returnIdsOnly is also enabled. This limitation helps manage the computational expense associated with comparing fields. Best Practice: To ensure data integrity and maintain access to historical records, it's recommended to enable syncRowsMovedOutsideFilter from the outset when setting up the service, especially if you plan to use fieldsToCompare in the future. This setup ensures that your system can accurately track changes across specified fields, even when data moves outside of defined filter criteria, while also managing computational resources effectively.

Workaround

Make sure to disable sync and change tracking if the existing service already turned on, if not then you can directly use UpdateDefinition on ADMIN REST API to {"syncRowsMovedOutsideFilter": true} Then enable sync and change tracking. Currently it only works with returnIdsOnly to true.