> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-customer-engagement/data-sync-jobs.md).

# Data Sync Jobs

This article describes the Entity Configurations tab in the Raptor Configuration app.

In the Data Sync Jobs tab, the user is able to define export packages for the D365CE Taxonomy job in Raptor. By defining a Taxonomy job, records from D365 CE can be automatically created as tags in the background. See [Jobs](https://docs.dynalogic.com/birds-document-warehouse-product-overview/setup-and-configuration/jobs.md) for more info.

To create a Data Sync Job click '+ New'.

Provide the following parameters:<br>

* Package Name: the name of your export

{% hint style="warning" %}
The following fields are obsolete and longer required:

* Cron Schedule

* AzureBlobContainerName

* AzureBlobStorageAccount

* AzureBlobStorageKey
  {% endhint %}

* Entities

Choose the entities you wish to export. Only the entities made in [Entity Configurations](https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-customer-engagement/entity-configurations.md)will be available.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-document-warehouse-product-overview/d365-customer-engagement/data-sync-jobs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
