Scenario – General Ledger transactions inbound
The customer has a requirement to import the following General Ledger transactions:
- High volume
- Batched
- File-based
Patterns
Consider the following patterns (best practices):
- Integrate data through Data Management API.
- Prepare data by using data integration tools, such as Azure Data Factory, and then send it to finance and operations apps through Logic Apps, Microsoft Azure Functions, or a Web activity in Microsoft Azure Data Factory.
Further information
The benefit of integrating data through Data Management API is that processing of such high-volume data through set-based operations is more efficient.
OData change sets can satisfy atomicity, and batches are slightly more efficient than individual calls but are still single-threaded.
Anti-patterns
Consider the following anti-patterns (pitfalls):
- Import through an Excel add-in.
- Create an OData call for each record.
- Run an OData batch.