> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.fynapse.app/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.fynapse.app/_mcp/server.

# Data Extraction for Microsoft Dynamics 365 Overview

> Learn about Data Extraction for Microsoft Dynamics 365 Overview in Fynapse.

## Overview

The **Extraction** functionality allows you to extract Journals automatically according to schedules defined by you to eliminate manual extractions. Extracted data can be later used by downstream services, for example, General Ledger.

## Overview of Data Extraction Process

The below description describes the data extraction process from the Fynapse GUI perspective. The complete process can be achieved through Fynapse GUI by using three screens:

* The **Extracts** screen displays all prepared extract configurations and lets you start defining a new configuration by clicking the **Add** button.
* The new extract configuration screen enables you to create extract configurations that allow you to extract a particular type of data using a defined query and triggering this extraction at a specific point in time with a required frequency. Configuring a new extract involves three major steps, that is:
  * Defining general settings such as a name, effective dates and time, a target name, and a configuration name
  * Building a particular data query to determine which data will be extracted
  * Configuring a schedule according to which the extraction will be performed or disabling it by selecting the **Disabled** option and manually extracting data by clicking the **Run now** button.
* The **Extraction logs** screen presents a list of already run extracts, as well as the ones currently in progress.

## Extraction Constraints

The maximum number of General Ledger Journal Lines in one extraction process is 4000 lines. If this maximum number is exceeded per one triggered extraction process, then data is split into extract batches (each with a different JournalBatchNumber and a maximum of 4000 lines).

> **Tip**
>
> To check how many batches constitute one extraction process, click the chevron in the **Details** column in the **Extraction Logs** screen. The list of all batches will be displayed.

Data with the same Voucher (that is, originating from the same transaction) cannot be split into different batches. That is why, if the limit of 4000 lines is reached then all lines having the same Voucher are moved to the new extract batch.

## Time Zone Support in Scheduler

Fynapse stores the times of a **Frequency** schedule in UTC. When you save the schedule, Fynapse converts the times that you enter from your local time zone by using the UTC offset that applies on that day. After a daylight saving time change, the extract configuration runs at the same UTC time, which is one hour earlier or later in your local time. To keep the same local time, edit the schedule after the change. **Specific dates** keep their local time, because Fynapse converts each date by using the UTC offset of that date.

To ensure proper work of a scheduler and guarantee that the extraction process will be triggered on configured dates and time regardless of a time zone in which you operate, some of the options available in the **Day** list when you select the **Yearly** and **Monthly** repetition options in the **Scheduler** panel are disabled. Additionally, there are some specific options available in the list:

* **Last** - means the last day of the month
* **Last - 1** - means the last day of the month minus 1 day. For example, if you select this option for April it will always imply 29th. If you select it for February it can imply 28th or 27th depending on whether it is a leap year or not.
* **Last - 2** - means the last day of the month minus 2 days
* **Last - 3** - means the last day of the month minus 3 days
* **Last - 4** - means the last day of the month minus 4 days

Look at some configuration examples to understand how it works.

#### Configuration Example 1

Let’s assume that you want to run your extract configuration monthly always on the last day of the month, then you need to select the **Last** option from the **Day** list.

#### Configuration Example 2

Let’s assume that you want to run your extract configuration yearly in February, March, and April on 29th then you need to select from the **Day** list for:

* February - **Last**
* March - **Last - 2**
* April - **Last - 1**

## Learn More

* [Extract Configuration](/documentation/microsoft-dynamics-365/data-extraction-for-microsoft-dynamics-365/extract-configuration-for-microsoft-dynamics-365)
* [Extraction Logs](/documentation/microsoft-dynamics-365/data-extraction-for-microsoft-dynamics-365/extraction-logs-for-microsoft-dynamics-365)