how to design parent child form in crm ?

(0) Share

Report

Posted on by Community Member

I m designing a school form in crm. It has these fields:

Student Name
Address
Email
Phone
Class
Admission Date
Class Admitted

I have used Contact entity and created a new entity AdmissionForm.

First is it good design i m trying to reuse Contact entity and use it for first 4 fields or I should add all fields in AdmissionForm ?

Many times user will directly come to 'AdmissionForm' form, how I can provide Contact fields on its form so that when user save AdmissionForm record, it should save data of contact field in contact entity and data of AdmissionForm in its entity ?

Please tell me if there is a better way to do this. I m new to CRM but have idea of its features. please tell what I should use.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Community Member on at

Like (0)

Report

"First is it good design i m trying to reuse Contact entity and use it for first 4 fields or I should add all fields in AdmissionForm ?"

Use the contact entity form imo. This gives you all the built in features you can have for that entity. You could also create a custom account form if you desired. I'll just assume for arguments sake you have 1:N (Contact :AdmissionForm)

Something like this in your contact form:

Contact:

=============

First Name

Last Name

Address

Email

Phone

...

[AddmissionForm (lookup)] <-- This sould be a custom field you add into contact that has a lookup to the AdmissionForm entity.

i.e. use a lookup to the students admission form.

Make sure that the data you want copied from contact -> Admissionform is of the same type (eg. Phone is string in contact, make Phone a string in Admission form). This is important later.

As for "it should save data of contact field in contact entity and data of AdmissionForm in its entity ?"

The answer is field mappings:

In your solutions explorer, click on 1:N relationships and then double click the new relationship you created earlier(eg. new_contact_AdmissionsForm) then click 'Mappings' > 'New', and start creating your mappings by selecting your source and target entity fields and clicking ok.

Was this reply helpful? Yes No
Suggested answer

Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

Using Contact Form is good choice for this case, if you do not think that you will need the Contact Form for a different purpose. In the Admission form, you should have a single field for Contact Id.

You can display the other fields on the Admissions form using Quick View Control.

If you need to display the other fields in the Admissions View, you can add the related columns to Contact as well.

Hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

- I added lookup in Contact

- data types are same and I added 1:N in Contact and in mapping (source Contact fields, target AddmissionForm fields)

Issue is when I fill Admissionform I have not fill Name in quick create form, second email address is not being saved to contact. any thing I should do further ?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Aric. But if display using quick view I will not able to add from admission form and to create a contact from admission form I will need to use quick create form. Is there a way I can avoid it and can use my form's simple field and create contact ?

Was this reply helpful? Yes No
Aric Levin - MVP 30,190 Moderator on at

Like (1)

Report

You will need to have some logic (i.e. plugin or workflow), that on the create event of a new Admission Record it will create a Contact record as well, and then store the recently created Contact Id back to the Admission Record.

The second issue with this is that you have to maintain it (on Update as well). If someone makes a change on the Contact record, you will have to update the respective Admission records, and if someone makes a change to the Admission record, you will have to update the respective Contact record. (Be careful of endless loops here).

I would use a Quick Create, so that I don't have to deal with that issues. Might be a little more work for the users, but it is the right way to do it.

Hope this helps.

Was this reply helpful? Yes No

Community site session details

how to design parent child form in crm ?

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Featured topics

Product updates

Community site session details

how to design parent child form in crm ?

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Featured topics

Product updates