Overview
On July 17th, 2024, Merge began automatically detecting and hiding newly created shell data records. Shell data records are objects where most fields are null except metadata, e.g., IDs, and timestamps. They can be temporarily created due to the ordering of model syncs. See the example below.
[
# normal application object
{
"id": "92e8a369-fffe-430d-b93a-f7e8a16563f1",
"remote_id": "98796",
"created_at": "2024-04-15T00:00:00Z",
"modified_at": "2024-05-16T00:00:00Z",
"job": "52bf9b5e-0beb-4f6f-8a72-cd4dca7ca633",
"source": "Campus recruiting event"
// ... other application fields
},
# shell data application object
{
"id": null,
"remote_id": "98796",
"created_at": "2023-07-15T00:00:00Z",
"modified_at": "2023-08-16T00:00:00Z",
"job": null,
"source": null
// ... other application fields are null
}
]
How does this affect me?
If you don't need shell data records | No action needed! Shell records will be hidden by default when you request data from Merge. |
If you need shell data records | To ensure that Merge continues to return shell data records simply include the query parameter |