You’re offline. This is a read only version of the page.
35
I have created a custom entity called "Event" with a number of attributes.
For each event it must be possible to enroll as participants a number of contacts.
It works perfect out of the box, by creating a 1: N relationship between Event and contact and the having a editabel subgrid for Contacts on the Event main form.
I can smoothly search for contacts to eb enrolled and create a new contacts if is does not exist.
BUT
I have the need to capture a few additional attributes for the contacts that are enrolled to the event - and now my problems starts.
I do not find it logical to populate the additional attributes on the general Contact entity as fields, as they then would appear on all contacts in the system.
I have tried to create e separate entity (EventParticipant) with a 1:N relationship ti Event with a contact field having a look-up to contact, but the I loose all the nice out-of-the-box functionality to enroll a participant(contact), as the EventParticipant has it own Primary Field - not being the Contact.
Can anyone come up with a good idea for a solution, where the enrollment of a participant (the "+" button in the subgrid shoud search for contacts) ?
*This post is locked for comments
I have the same question (0)
Share
Report
All responses (
Answers (
