Skip to main content

Notifications

Announcements

No record found.

Customer Service forum

Auto Case Creation Default Customer and Contact fields

Posted on by 15

I am finding conflicting information as well as seeing different results as part of my testing so I need clarification on some issues we have came across when using the Customer Service Auto Case Creation. Our organization would love for all emails that come into the Service Desk queue to have the "customer" be a CRM contact exclusively.  When a contact does not have an account listed on their record this works perfectly.  However, when they do, it puts the account in as the Customer and their name in as the Contact. 

This makes it very difficult to set up the email templates to fill in information for the Contact.  If I reference "customer" as the email recipient but the customer happens to be an account, my workflow triggers an error.  If I set it as contact, but the contact is listed as the Customer, then there isn't a contact to send the email to and I receive another error.  

I have been working some time on trying to determine how to get these fields to operate how they should without causing lots of extra work on our technicians to make sure all contact information is entered manually with each case.  I would love to have all cases list the email sender as the customer, no matter if they have an account listed or not.  

I found information via research stating that if we change the default auto case creation fields for customer or account it will not work properly, but those were dated 2015 and there was info saying it was slated to be updated in the following spring release.  But there is no new information on if this has changed and the {null(Channel Properties)} can now be changed or not.

I also found a solution being offered by Work 365 called Email to Case Automation that will do this as well as other things we are looking to do like fill the email body information into the Description. I like to try not to use add ins and make solutions in-house so I would like to make sure the features for auto case creation field values for Customer and Contact cannot be populated as we wish to do natively before going to another solution.  

Any help anyone can give would be greatly appreciated. 

  • Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at
    RE: Auto Case Creation Default Customer and Contact fields

    In this case,

    You can modify your below scenario:

    CRM will give error when you try to update contact record to "Contact" field...if Contact's parent account has not been set as Case.Customer...

    To

    Create a contact lookup on case entity and always update this lookup as per customer lookup.

    If customer lookup is account then set primary contact to this new lookup field, if Customer is contact then copy same contact in this field.

    I did not say to leave customer field as blank.

  • Zap Objects Profile Picture
    Zap Objects 913 on at
    RE: Auto Case Creation Default Customer and Contact fields

    Hello Rocker,

    In regards to point:
    ====
    Write a plugin on create of case that will check if customer is account then set it's primary contact in "Contact" field of Case entity and if customer is contact then also set same same contact in "Contact" field of case entity and use "Contact" field in your workflow rather than customer.
    ====

    CRM will give error when you try to update contact record to "Contact" field...if Contact's parent account has not been set as Case.Customer...

    In order to get around this issue, in our email-to-case app... we have created a custom contact field called as "Sender Contact"... this is always updated with the Contact record which matches the senders email address...
    For more details refer:
    https://appsource.microsoft.com/en-us/product/dynamics-365/zap.zap_helpdesk-email-to-case

  • Suggested answer
    Dynamics365 Rocker Profile Picture
    Dynamics365 Rocker 7,755 on at
    RE: Auto Case Creation Default Customer and Contact fields

    There are two solution of your problem:

    1. Copy primary contact email in your account email and use "Customer" field in workflow.

    2. Write a plugin on create of case that will check if customer is account then set it's primary contact in "Contact" field of Case entity and if customer is contact then also set same same contact in "Contact" field of case entity and use "Contact" field in your workflow rather than customer.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans