Ace Your MB-700 Dynamics 365: Finance and Operations Apps Solution Architect Expert Exam

Data migration is a key success factor in almost every implementation. A primary concern of some customers is the speed that data can be migrated at, especially if there are vast amounts of data and a small cutover window. The Data migration framework is also used to move data as part of business requirements and operations.

A data package for a Dynamics 365 Finance and Operations app can consist of one or many data entities. A typical data package consists of a group of entities for a specific task, process, or function.

Note: A mock cutover was conducted. It was unsuccessful due to lack of coordination across the countries. The lack of success created timing issues with data uploads from centralized IT and validation at the country level. User1 must use a standard template to prevent the mock cutover issue happening at go-live.

Box 1: Consolidation company

Eliminations can be reported in multiple ways:

* A separate company can be created and used to manually determine and post elimination transactions. This company can be used in the consolidation process or in financial reporting.

* Elimination rules can be set up in the system.

* The accounts and financial dimensions that are used to determine intercompany activity can be filtered on a row definition or column definition in Financial reporting, and full drill-down capabilities can be used.

Box 2: Financial reporting

There are multiple options for consolidating data:

* Financial reporting – This option enables consolidation of transactions and balances, and can be generated at any time. Multiple levels of hierarchies can be created, and multiple reporting currencies can be viewed.

* Consolidate online – This option consolidates daily balances by the selected accounts and dimensions, and stores them in a consolidation company.

* Consolidate with import – This option imports balances into a consolidation company.

Export company balances

Note: The CEO is considering the acquisition of additional companies in the same countries as the current companies. The consolidation structure may change within the first 90 days of go-live. Margie’s does not want to finalize the consolidation structure for a hard-close at month’s end until this has been finalized.

Note: Once user acceptance testing (UAT) has been completed, the project manager must report the number of tenants for production to Microsoft.

Go-live Readiness Review prerequisites

The project team should validate solution readiness. The following prerequisites must be met before the Go-live Readiness Review with Microsoft can be initiated. The production environment can be deployed after the Go-live Readiness Review with Microsoft has been successfully completed.

* User acceptance testing (UAT) and performance testing have been completed or almost completed in a Tier-2 (or higher) environment.

* The environment version that is planned for the go-live complies with the Software lifecycle policy.

* The environment version that is planned for the go-live complies with the Software lifecycle policy.

* All licenses that are required for go-live have been purchased in the correct tenant.

* Etc.

AOT deployable package – A deployable package that is generated from application metadata and source code. This deployable package is created in a development or build environment.

Note: Margie’s Travel offers consumers a loyalty program. Consumers can earn points per dollar spent across all in countries in which Margie’s operates. The loyalty program is currently managed by using a spreadsheet.

The infrastructure team must move the code for the loyalty program to test environment.

Margie’s Travel learns that the loyalty program across multiple countries is not a standard industry process and is not a standard feature in Dynamics 365 Finance.