Hello
I try to add a calculated field to the case/incident table, but I am not able to choose the customer/account/contact relationship.
CustomerId, AccountId and ContactId are not available to choose in the action nor in the condition dropdowns.
How can I add a calculated field to the incident table, based on a field on the account/contact/customer table?
Hi,
Please refer to the following link to use related entity field.
Dynamics 365: Use a Field in a Related Entity in a Calculated Field - The Marks Group | Small Business Consulting | CRM Consultancy
First find the name of lookuo field in Case entity just like this, I find it in relationship, you can also find it in column directly.
Then follow the tutorial to enter "primarycontactid", now you can choose them.
Hello Eiken
Thank you for the feedback.
I cannot find the entity "CustomerId" within the calculated field:
In addition, I cannot even access the customer/Account entity from a calculated Yes/No field:
Any further idea?
Thank you.
BR
Raphael
Only look up field with relationship can be found in that way in calculate field, but the CustomerId's data type is customer,so it correspond to two entities: Account and Contact.
This is also the case in the a calculated Yes/No field.
You can create a lookup field and associate it with the account entity. Then use this filed to edit calculate field.
Hi again
As far as I understand, the Customer field is responsible for the mapping from Case to the Account/Contact.
When I add an additional Lookup field for the account, I have to change the default way the system works or somehow populate the account otherwise, haven't I?
Or will the field automatically be populated when I choose an account as customer?
I'd like to keep the system logic as standard as possible. Maybe it would be safer to update the fields with a flow.
Yes, you can update the custome look up field when you choose an account with a flow or business rule.
But if your customer has both contacts and account, you need to determine if it is a contact or an account.
Would you please tell me what you need this calculated field for.
Hi Eiken
Well I would like to do it otherwise, which means updating the account id from the customer field.
Maybe a business rule will do the trick if it does not work otherwise.
So basically what I want to achieve is to have 2 fields on the case form that are already available on the account form (1. field is to determine if the customer is blocked or not, so he gets no support and the 2. field is the customer priority level normal, high or VIP).
The supporter should then get a message box / pop up which should inform about a VIP/High and blocked customer.
In CRM 2016/8.2, I managed to do that with two workflows and javascript code (to show the message box). I hoped that there would be a better solution in the meantime, which would be perfectly solved with a calculated field.
Any idea?
Thanks!
Hi
I managed to do it with a Quick View and JavaScript (formContext.ui and notification), so there is no need anymore for a calculated field.
The quick view looks much better as it did in CRM 8.2, so I think we will go with that.
Thank you anyway.
Best regards
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Tom_Gioielli 49 Super User 2025 Season 2
MVP-Daniyal Khaleel 46
CU23101130-0 17
