After importing a Dynamics 365 solution into another environment and publishing the customization, you many think your deployment is complete. However, there may be some post-deployment steps you need to take to ensure desired customizations are achieved.

Here's a list of steps you will want to check:

1. Duplicate Detection Rules

If your solution included entities that have Duplicate Detection rules published, you will need to re-publish them after deploying your solution as they become unpublished when the related entity metadata is updated (even if it doesn't change).

2. Workflows

State: If the Workflow already exists in your target organization any updates to the workflows state (Activated or Draft) will not be updated via solution import. Check your Workflows in your solution to ensure each is at the proper state.

Owner: The owner of a Workflow is replaced with whatever user you are importing the solution as. Ensure Workflow owners are correct after importing a solution.

Lookup References: If lookups were referenced in your Workflow, you many need to check to ensure that the lookup reference is resolving. If not, you will need to modify the lookup reference to the proper record in your current organization. (This step can be prevented by ensuring record GUIDs for these lookups are the same across your organizations).

3. System Views

State: The state of System Views is not included in a solution. Therefore, if you wish to deactivate any system views you must do so in each environment.

4. Business Rules

State: If a Business Rule already exists in your target organization, any updates to the Business Rule State (Activated or Deactivated) will not be updated via solution import. Check any Business Rules included in your solution to ensure they are in the correct state.

Lookup References: If lookups are referenced in your Business Rule you many need to check to ensure that the lookup reference is resolving. If not, you will need to modify the lookup reference to the proper record in your current organization. (This step can be prevented by ensuring record GUIDs for these lookups are the same across your organizations).

5. SMOKE TEST

New/modified Components: Test each new or modified component. *It can be easy to forget to add certain dependencies to solutions, so ensure the system is behaving as expected.

Existing Functionality: Test existing functionality throughout the system to ensure that changes made do not adversely affect existing system functionality.

Security Roles: Ensure you use different security roles (other than System Admin) to make sure there are no security restrictions that can negatively impact a user's experience.

Hopefully this checklist helps you ensure your customizations were made! For more Dynamics 365 tips and tricks, subscribe to our blog.

Happy Dynamics 365'ing!