web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Workflow creation of C...
Microsoft Dynamics CRM (Archived)

Workflow creation of Case fails because case is missing customer after 2016 upgrade

(0) ShareShare
ReportReport
Posted on by Community Member

We have several processes that create cases for our users via workflows. In 2015 I was able to set the customer value using a dynamic slug within the workflow at the case creation. After our on premise upgrade to 2016 sp1 there is now a new field on the case entity called customer that doesn't give me any options to get into the details of the field to turn required off. Has anyone else come across this? If so how did you resolve the issue for setting the customer dynamically.

Thanks! Jenn

*This post is locked for comments

I have the same question (0)
  • razdynamics Profile Picture
    razdynamics 17,308 User Group Leader on at

    Hi Jennifer, The Customer lookup can be either Account or Account. The Customer Field on the Contact is usually used to Identify the Parent Account of the Contcat so this will make it difficult to perform the operations on Contacts.

    One Work around is to Create a Custom lookup to Account on the Contact Entity called new_parentAccount and Add it to the 1:N Relationship Mapping on the Account, allowing this lookup to be used instead of the Customer lookup which has the limitations.

    Best Wishes, Raz

  • Community Member Profile Picture
    Community Member on at

    Unfortunately this does not resolve the issue. Creating the 1:N relationship causes the field to populate with a mapping to the account record. It is this very system mapping that we are trying get rid of or overwrite. We can write javascript to clear the value that is coming through but can not create a new mapping to the field because the field we need to map to is already in use. Therefore we were going down the avenue of javascript to pull the value from the account to the opportunity but I can not seem to get from the opportunity to the account to the value of a field on the account via the relationship of potential account.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans