As it stands at the moment, using an automatic record creation rule to create cases from an incoming mail queue will not prefil in the system and placed into one of the emailaddress(1/2/3) fields on the account for both the Customer and Contact field on a created record if the sending email address is both a pre-existing Contactm. As confirmed by a Microsoft support case, the Account will take precedent, therefore only the Account will be place on the created record, instead of the Account and Contact. In my mind, this is not expected system behaviour, but currently that is how Dynamics will work, confirmed by the PG. I would like this changed so that it will create a record using both the Account and Contact record linked correctly instead of just the Account.

Needs Votes
Ideas Administrator

Thank you for your feedback.

Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.




Fully agreed,
Firstly We use Customer (Mandatory) field and on FormLoad we do filter only Contacts to be shown so Microsoft gives us the ability to filter only Contacts for the Customer field but through Record Creation and Update Rule it Populate Customer of the Contact if there is a Customer associated with the Contact.
Secondly Contact lookup field is not mandatory but the Record Creation and Update Rule forces this field to be filled and we if the Contact has a Customer associated , we cannot fil both Customer and Contact as Contact as explained by Microsoft scenario 3.

So I consider this as a Bug rather than by design/Design limitation.

Reference - 120062223000173 Microsoft Case number.


Category: Automatic Record Creation