Previous

Next

Summary

Completed

In this module, you remotely managed IoT devices using the Dynamics 365 Connected Field Service solution. There are several items to go into monitoring and servicing remote devices.

We explored some of these items including:

• Examine the relationship between customer assets and IoT devices.

• How to interact with devices using commands.

• How to use some of the out of the box actions to help with automation.

• How to build business process flows that CFS can use.

The next steps from here would be to gain a deeper understanding of interacting with devices. This would include understanding how device twins can be used to report and query information. You should also explore some of the other features available for interacting with devices using commands. This would include items like device categories and command and property definitions.

Clean up your environment

If you're done, and ready to clean up your environment we need to remove all the items that we created in this exercise. During this exercise, we created a solution to store all the customizations, workflows, and business process flows that we created. This was done to not only make it easier to keep our changes together, but to also help with the removal of these items upon completion of this module.

When you remove an unmanaged solution from Dynamics 365, it only removes the container that groups the customizations together. Each customization would need to be manually removed from the system in a specific order. Rather than having to manually removing each process, relationship, and customization is a specific order, it's easier to remove all the items at once. This can be done by using a managed solution. When you remove a managed solution, it removes all the items included in the solution as well. This is the process that we use.

To fully remove all the items in the system, follow these high level steps

• Export the IoTAlertProcess solution as an unmanaged solution. (This serves as a backup if you ever want it in the future, or if we have problems).

• Export the IoTAlertProcess solution as a managed solution. (This is installed back into your environment).

• Delete the IoTAlertProcess unmanaged solution from your environment. (This step removes the container to make importing the managed solution easier).

• Import the IoTAlertProcess managed solution into your environment (This step converts all the customizations to managed components).

• Delete the IoTAlertProcess managed solution from your environment. (This step acts as an uninstall and fully removes all of the changes we made from your environment).

Detailed steps

1. In Dynamics 365, navigate to Settings > Solutions.

2. Select the IoTAlertProcess solution.

3. Select the Export button and follow the steps to export it as an unmanaged solution. Save the solution somewhere where it's easy to find.

   • Make sure all your customizations are published.

   • Ignore any dependency or missing components messages since we're just importing it back into the same environment.

   • The file exports with a name of IoTAlertProcesses_1_0_0_0.zip.

4. After the export process is complete, select the Export button again and follow the steps to export the solution as a Managed solution.

   • The file exports with a name of IoTAlertProcesses_1_0_0_0_Managed.zip

5. With the IoTAlertProcesses (unmanaged) solution still selected, select the Delete button to remove the unmanaged solution from your environment.

   • Remember: This process only removes the solution container. All customizations remain.

6. Select the Import button and follow the prompts to import the IoTAlertProcesses_1_0_0_0_managed.zip file into your environment.

   • Ignore any warning messages that appear.

7. Ensure the IoTAlertProcesses (managed) solution is selected, select the Delete button.

All of the fields, form changes, workflows, and other customizations that we made are now fully removed from your environment.

Optional: Remove Azure Resource Group

Important

You should only follow these steps if you are completely done with your Connected Field Service environment and do not plan on taking any other modules or doing anything else with it.

When you deployed the Connected Field Service add-on, it created an Azure Resource Group in your subscription that contains all the components of the template. If you're going to complete other learning soon, you might want to wait to do the cleanup until you have completed any of the other modules that require a Connected Field Service deployment.

If you're done and ready to clean up, all you need to do is delete the resource group in Azure. You can accomplish that in two ways, either via the Azure portal or from the Azure Cloud Shell.

Via the Azure portal

1. Navigate to the Azure portal.

2. On the left side, choose Resource Groups.

3. Type your resource group in the filter by name or find it on the list.

4. Select the Resource Group to open the detail page.

5. After confirming it's the right Resource Group, select all the items in the group and select Delete.

Via the Azure Shell

1. Navigate to Azure Shell.

2. List your accounts using command: az account list.

3. Select your account using command: az account set -s "My Account Name".

4. Delete the resource group using command: az group delete -n "Your Resource Group Name".

Continue