D365 F&O Integration Best Practices, Patterns and Anti-Patterns¶Updated
Scenario # 1 - High volume, batched, file-based GL transactions¶
The customer has a requirement to import GL transactions: High volume, Batched, File-based
Patterns¶
GL transactions integration - Inbound
-
Data integration through Data management API.
-
Data can be prepared using data integration tools, for example Azure Data Factory (ADF), then sent to F&O via Logic Apps or Azure Function or ADF Web Activity.
Anti-Patterns¶
-
DO NOT Import through Excel add-in
-
DO NOT use OData call per record or OData Batch