Missing Contact Information Form After Upgrading in Dynamics 365

Miguel Nepomuceno, 24 September 2018

Upgrade season is upon us! On my previous blog, Microsoft has been pushing clients to upgrade to more updated versions of Dynamics 365 Online, making it mandatory for customers with v8.0 or v8.1 to upgrade to v8.2. Microsoft are also incentivizing customers to upgrade to the latest version of Dynamics 365 by stating that they will only be supporting v9.0 from February 1, 2019.

With customers having to book dates or conduct upgrades with Magnetism more frequently, we have encountered a lot of weird issues after an instance version upgrade.  The main issue is that customers are reporting missing components in their system. They are left wondering where certain fields are in the form, specifically dealing with the Contact entity. After further investigation, I have been getting same issue from different customers regarding one specific component – the Contact Information Form always goes missing after an upgrade.

The Contact Information Form is an out-of-the-box System Form, and this is used by most of our customers when managing their Contact records. This out-of-the-box Form frequently contains custom fields and other custom logic. You can imagine how frustrating it is for our customers, especially if this Form is vital to their everyday business tasks.

If you are getting this issue, don’t fret. What you need to know is that Forms can also be deactivated. You simply need to check in the Default Solution (Settings > Customizations > Customize the System) under Entities > Contact > Forms. There is a dropdown for System Forms which you need to filter to Inactive Forms where you can find the deactivated Information Form.


After identifying the Form as Inactive, you just need to select the Form, click the Activate ribbon button, and Publish.

While this is a nuisance, I am hoping this blog will point you to where to look for and search incase this happens after your instance version update. I have not seen other cases with this issue for other Entities and other System Forms after a version upgrade.