Skip to main content

Completed 2023-04-11: Changes to handling of deleted data

ยท 2 min read
Daniel Laing

On April 11, 2023, Codat will change the way accounting data deleted by company users within their accounting package is handled.

To ensure better consistency between successive data syncs, records deleted by a company between two data syncs will now continue to be stored by Codat. A flag will be set to indicate that the data has been deleted in the underlying Accounting package.

Update - 2023/02/16

This was previously scheduled for 2023/04/10. This has been pushed back a day as this fell on a public holiday in the UK.

Action requiredโ€‹

From April 11, 2023, the Codat API will return data that was not previously returned. Therefore, if data pertaining to records deleted between two successive data syncs is not required for your use case, you will need to filter out deleted records. This can be achieved by querying Codat's API with:

Expected impact if no action is takenโ€‹

If no action is taken, API calls to retrieve company accounting data will include records deleted by companies.

Additional informationโ€‹

Accounting data deleted by a company between two data syncs can be identified with the isDeleted flag (boolean), present on the metadata object that is now returned on all Accounting data endpoints.

"metadata": {
"isDeleted": true // false by default; true only where previously synced data is deleted by a company

Note 1: This change applies to only Accounting data deleted by a company between successive Codat data syncs. Records that were both created and deleted by a company before the first Codat sync will never be included in Codat data.

Note 2: For datatypes with a Status property in Codat's data model, Codat does not currently delete data, but instead updates the status property. The metadata.isDeleted flag will be set to True after April 11, 2023.

Note 3: For pre-existing data, the isDeleted flag may be set to null; this will be set to true/false on future data syncs.

Get ahead

You can get ahead of this change by enabling it now in the Portal. Learn how to do that here, or read our change policy.