AXtend Data Management simplifies complex data migration and integration tasks by combining SQL Server’s power with Dynamics 365 for Finance and Operations data entities. It automates imports with robust error-handling tools.
User Guide: This guide walks IT professionals through AXtend Data Management’s features and optimal configuration. It’s intended for those experienced with Dynamics 365 for Finance and Operations and its Batch and Data Management frameworks. Familiarity with basic SQL Server Database Engine operations, like database restoration and executing stored procedures, is also assumed.
Support and Contact: For assistance or to see ADM in action before trying it yourself, contact us at axtend@axtenddynamics.com.
Data Handling: ADM comes with a predefined database schema, including table structure and stored procedures. The Azure staging database is loaded with configuration and base settings from the D365F&O database for validation. Data extraction, cleaning, and transformation occur before loading it into an Azure staging database extract table. Before imports, stored procedures validate Azure staging database data for consistency and mandatory field completion. Data is also validated against D365 F&O configuration in the target environment.
Pre/Post Processes: ADM introduces pre- and post-processes that can perform various tasks. These processes are useful when you need to modify parameters before and after data management execution, such as enabling manual entry for a main account during import and then reverting it after import completion.
Import Methods: Data can be imported in two ways: single imports or import templates. An import requires an import batch setup that specifies the legal entity for data import. All imports run within D365 F&O using the Batch jobs feature. ADM is a multithreaded application, which means import execution is divided into multiple batch tasks (threads) to enhance speed.
Import Templates: Import templates group imports and processes, controlling their execution sequence. When a template is executed, it creates a monitoring batch job that sets up all batch jobs and ensures they execute in the correct order.
The following figure offers a simplified overview of the solution and its functioning at a glance.
