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) / Entity Inheritance
Microsoft Dynamics CRM (Archived)

Entity Inheritance

(0) ShareShare
ReportReport
Posted on by Community Member

Hi All,

I am trying to extend the Case entity under Services. I am adding three lookups

1 - Product

2 - Category

3 - Sub Category

Based on the selection of these lookups, the information that I want to collect differs, for example in some cases I only need description text, in some I need 10 different fields.

What is the best approach to handle this? Should I create one big entity and create different forms? Or is there a better want to handle

*This post is locked for comments

I have the same question (0)
  • Wayne Walton Profile Picture
    Wayne Walton 13,730 on at

    I recommend looking at Business Process flows.  you can set up rules to show and hide fields based on how other fields are filled out.  Then you would store most everything on the Case, and just update the layout of the form based on how they fill things out.

  • Community Member Profile Picture
    Community Member on at

    I am wondering if there can be an efficient way of doing this rather than dumping every field in one entity?

  • Verified answer
    Wayne Walton Profile Picture
    Wayne Walton 13,730 on at

    Adding more entities only adds more work for your end-users, in my opinion.  Keeping it all as part of a Case and then moving the data where you need on the back-end makes their jobs easier even if setting it up is harder.

    Plus, I'm not sure what kind of savings you're going to get when you have to make those other entities and then try to link everything up.

    Alternately, you could set up Dialogs to capture what you want and store the captured data on the Case.

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    I agree with Wayne that a single entity is probably the best model here unless there are many tens or hundreds of different fields involved. use Business Rules or javascript to conditionally display the correct fields / sections to users, or use Business Process Flows to capture the data and switch processes depending on earlier answers (ideally the first set of fields captured on record creation, made business required to force users to answer them)

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