With this type of data integration, more than one record is normally processed. These types of processes don't execute when records are modified; instead, they wait for a specific time period to initiate data integration. The following diagram represents the high-level idea of batch processing:

As you can see, this process is associated with a timer logic that waits for a specific period. Normally, it runs after office hours, when no one is using the system. There is a logic associated with this process, which fetches data from the source system based on some criteria; for example, it may want to send records that were modified today.

Both integration options utilize the Dynamics 365 CE API to work with Dynamics 365 CE data. We can use utilities developed in-house for this data integration, or we can use different connectors that are available on the market for these integrations.