Scenario 1
The teacher of a class wishes to maintain the attendance records of every student in any given year.
The standard behind designing any solution in Microsoft Dynamics CRM 2016 is to avoid as much custom code as possible. It makes the customizations easy to maintain and upgrade if we end up moving to newer versions of CRM. Here, again, we will try to achieve the same.
As stated in the mapping section, we identified that Attendance of any student can be captured as a custom activity record. The following steps explain how the scenario can be achieved:
- Creating the attendance entity: In the following screenshot, review the
Define as an activity entitycheck box:
Scenario 1 : Attendance entity
On creating the entity, a 1:N relationship between Contact and Attendance should get automatically created:
Contact relationship
Note
When we say that a 1:N relationship exists between entity A and entity B, we mean that one record of A can be connected to multiple records of B; however, one record of...
