Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some or all of the functionality noted in this topic is available as part of a preview release. The content and the functionality are subject to change.
This article describes application lifecycle management (ALM) in Microsoft Dynamics 365 Intelligent Order Management. It includes information about how to move solutions from one environment to another or package solutions for storage in source control.
The following information specifies the setup tables that are required to migrate data for Dynamics 365 Intelligent Order Management configurations. These setup tables require a manual step to add each entity to an unmanaged solution. After the desired entities are added, the solution can be exported via a package file that contains the data of the entities that were added to the unmanaged solution. The package file can then be imported into another Intelligent Order Management environment, where the data can be activated for use.
Setup tables
The following table lists the setup tables that are required to migrate data for Intelligent Order Management configurations.
| Table name | Solution location |
|---|---|
| Policy (msdyn_iompolicy) |
Intelligent Order Management Provider Integration Outbound |
| Rule (msdyn_iomrule) |
Intelligent Order Management Provider Integration Outbound |
| Provider Definition (msdyn_iomproviderdefinition) |
Intelligent Order Management Provider Configuration |
| Provider (msdyn_iomprovider) |
Intelligent Order Management Provider Configuration |
| Provider Connection Reference (msdyn_iomproviderconnectionreference) |
Intelligent Order Management Provider Configuration |
| Provider Definition Connection Reference (msdyn_iomproviderdefinitionconnectionref) |
Intelligent Order Management Provider Configuration |
| Provider Transformation (msdyn_iomprovidertransformation) |
Intelligent Order Management Provider Integration Base |
| Provider Transformation Definition (msdyn_iomproviderdefinitiontransformation) |
Intelligent Order Management Provider Configuration |
| Provider Parameter (msdyn_iomproviderparameter) |
Intelligent Order Management Provider Configuration |
| Provider Definition Parameter (msdyn_iomproviderdefinitionparameter) |
Intelligent Order Management Provider Configuration |
| Provider Definition Logic Definition (msdyn_iomproviderdefinitionlogicdefinition) |
Intelligent Order Management Provider Configuration |
| Designer (msdyn_iomdesigner) |
Intelligent Order Management Designer |
Tables required for policy rule migration
The following tables are required for policy rule migration:
- Policy
- Rule
Note
When you manually add rules, the parent policies are automatically added.
Tables required for provider migration
The following tables are required for provider migration:
- Provider Definition
- Provider
- Provider Connection
- Provider Connection Reference
- Provider Transformation
- Provider Definition Transformation
- Provider Parameter
- Provider Definition Parameter
Tables required for orchestration migration
The following tables are required for orchestration migration:
- Designer
- Policy and Rule tables
- Provider tables, if orchestration has provider actions.
Add tables as solution components and export your solution from the source environment
To add tables as solution components and export your solution from the source environment, follow these steps.
Go to https://make.preprod.powerapps.com for your test environment or https://make.powerapps.com for your production environment.
In the upper right, select the appropriate environment.
In the left navigation pane, select Solutions.
On the Solutions page, set the solution preview option to Solution preview off.
On the toolbar, select New solution.
In the New solution dialog box, follow these steps:
- Enter values in the Display Name and Name fields.
- Select any publisher.
- Leave the version set to 1.0.0.0. The version number can be increased as you export solutions and is required to upgrade a managed solution.
- Select Create.
Open the new solution.
On the toolbar, select Add existing > Table.
In the Add existing tables dialog box, find or search for a table that is required for the data migration, and then select it. The search field is located in the upper right.
Find and select the rest of the required setup tables, and then select Next.
Under Selected tables, select the Include table metadata checkbox for each table.
Select Add.
After existing data has been added to the solution, select Export on the toolbar.
In the Before you export dialog box, under Publish All Changes, select Publish, and then select Next.
In the Export this solution dialog box, under Export as, select Managed (recommended), and then select Export. This export option creates the package zip file that contains the data that was added as a solution component.
Wait for the export to be completed, and then download your solution. The solution might be downloaded automatically. Therefore, check your local Downloads folder when you see the export success message that has a green background.
Import your solution into your target environment
To import your solution into your target environment, follow these steps.
- In your target environment, in Intelligent Order Management, ensure that your orchestrations, providers, and policies are deactivated/unpublished. You must complete this step for each provider, policy, and orchestration that you're importing.
- In your maker portal (https://make.preprod.powerapps.com for your test environment or https://make.powerapps.com for your production environment), select the target environment that you want to import the solution into.
- On the toolbar, select Import.
- Import your solution into the target environment. Then activate policies, providers, and orchestrations, in that order. After the components are activated, the flows for policy will be updated, and orchestration flows will have to be republished with the data that was imported.
Policy and rule versioning
To enable changes to be rolled back to a specific version for policy and rules, versioning records are created for the policy components.
In the policy table, there are two states for records:
- Current – There is only one current record for the policy.
- Archived – There can be many archived records, depending on the number of changes that have been made to the linked policy and rules.
An archived version of the policy will have appropriate rules linked, based on the policy ID. The versioning record is created every time that a policy is unpublished.
The following tables highlight how the two tables are linked and how the PolicyVersionId column is used to group the versions that are created for a policy. The PolicyVersionId column is filled with the policy ID of the first policy record that was created. The policy ID value will persist for each subsequent version that is created, whereas the PolicyId column will be filled with a new globally unique identifier (GUID), together with a new rule that is created to link to that new GUID.
| Policy | Type |
|---|---|
| Primary Key (PK) PolicyId | GUID |
| PolicyVersionId | GUID |
| PolicyVersionState | enum |
| PolicyVersionNumber | int |
| Rule | Type |
|---|---|
| Primary Key (PK) RuleId | GUID |
| Foreign Key (FK) Policy | GUID |
| RuleDefinition | string |
| AssociatedEntity | enum |