From the Microsoft Dynamics CRM Blogs: Custom fields, biz rules in Dynamics 365; Conquering ActivityParty; Fix broken case forms

A selection of the latest insight from the Dynamics CRM blogs:

• In Dynamics 365, Sometimes Custom Is the Way to Go
• Business Rules - Dynamics 365
• CRM 2016 - ActivityParty and ActivityParty Lists
• Beware of Legacy Forms and How to Fix Broken Case Forms After Upgrade

In Dynamics 365, Sometimes Custom Is the Way to Go

On the Ledgeview Partners blog, Chad Collett stated that Microsoft Dynamics 365 allows organizations to capture important information right out of the box. And the configuration that's necessary to capture pertinent information can often include adding out-of-the-box fields to a form.

Sometimes, however, Collett stated that it might make sense to create a custom field even though an out-of-the-box field seems to be available.

For instance, you may have a situation that requires capturing multiple addresses directly on the lead, account, and contact forms, and you have to identify address types that are unique to your business. But the "Address" entity in your case isn't really a practical option for users, according to Collett.

You could use the standard "Address Type" option set fields and add or change the existing options, although this is option is a bit complex, he noted.

An alternate solution is to create custom address type fields that utilize a global option set. It may take a few more minutes to set up initially, but long term the convenience and reduced risk of issues make it worthwhile.

You can learn about this solution here.

Business Rules - Dynamics 365

On its blog, the  Inogic team observed that a number ...