The first time an incremental load job runs to capture change data for a Zendesk source, the job retrieves and loads only the change records that are created after the date and time specified in the associated ingestion task. You can specify the date and time when you configure the source in the

application ingestion

task wizard. However, when you resume a stopped or aborted job, the job begins propagating change data from where it last left off.

Incremental load jobs and combined initial and incremental load job configured for Zendesk sources do not detect and replicate the changes that are made to the source schema.

If a source record contains multiple custom fields,

application ingestion

jobs store the data of all the custom fields as a JSON object in a single column of the target table.

Application ingestion jobs can retrieve data from the custom fields that are present in the following Zendesk objects:

Organizations
Requests
Tickets
Users

Initial load jobs propagate null values for the data stored in the following Zendesk fields:

dns results field in the Support Addresses object.
raw request and raw response fields in the Target Failures object.
reason code field in the Satisfactory Ratings object.
URL field in the Sharing Agreements object.

Initial load jobs do not propagate the data stored in the following Zendesk objects:

Attachments
Channel Framework
Dynamic Content Item Variants
End users
Incremental Skill-based Routing
NPS
®
Invitations
NPS
®
Recipients
NPS
®
Responses
OAuth Tokens for Grant Types
Push Notification Devices
Search
Side Conversations
Side Conversation Attachment
Side Conversation Events
Skill-based Routing
Ticket Comments
Ticket Import
User Identities
User Passwords

Mass Ingestion Applications

can capture change data for the following Zendesk standard objects:

NPS Recipients
Organizations
Side Conversation Events
Tickets
Tickets Metric Events
Users

Incremental load jobs can capture the deletion of records that are stored in the following objects:

Organizations
Tickets
Users

Mass Ingestion Applications

does not replicate the hierarchical structure of the source fields of the type Object. On the target table, all fields are at the same hierarchical level. When an

application ingestion

job replicates an Object field with multiple hierarchical levels, the job creates the corresponding columns at the same hierarchical level.