Hi team,
The export file that gets produced as part of running the F1-GEEXO (ongoing generalised data export - GDE) batch is a JSON, which brings across the list of maintenance object records that have experienced a data change (or new record) in the system since the previous GDE.
The payload for each key record is the entire maintenance object record with all child table values.
I’m proposing an addition to the record payload below to include another element to show whether that record is a new record or updated. The line 2337 in the screenshot below would then look like this for a brand new activity:
{"OBJ":"W1-ACT","TIMESTAMP":"2025-11-11T01:33:55.000445Z","PK1":"00394583636902",”NEW”:”true”,"DATA":{"W1_ACTIVITY":[{"ACT_ID":"00394583636902","BUS_OBJ
Any subsequent change to the record after the GDE would have the NEW flag removed from the payload:
{"OBJ":"W1-ACT","TIMESTAMP":"2025-11-11T01:33:55.000445Z","PK1":"00394583636902","DATA":{"W1_ACTIVITY":[{"ACT_ID":"00394583636902","BUS_OBJ
This would allow us to greatly improve the performance of our change data capture process in downstream data pipelines to in advance more easily detect new records v updated records and bypass our source v target comparison required to determine changes in each maintenance object table.