|
netwerker
|
April 18, 2019 at 9:51 am
We have the following use case / problem:
- We have a page with multiple events
- For each event you can sign up for yourself and 1..n other people
- No we had the following situation:
- User A made a registration for Event 1 together with Mister B
- User C made a registration for Event 2 togehter with Mister B (same name and same physical person but different event)
A few days later we got the message from User C that Mister D will attend Event 2 with him instead of Mister B.
We changed Mister B to Mister D in registration of User C for Event 2
Problem: Mister B was also changed in registration of User A for Event 1
I hope you can follow my description?
My question is how we can ensure that this doesn’t happen? It seems that you only use the joined personal details of one person as unique key?
I hope you can help me.
|
|
netwerker
|
April 18, 2019 at 9:52 am
Sorry for bad format but I didn’t find a solution to edit my post again?
Thx in advance for your help
|
|
Josh
|
April 18, 2019 at 9:58 am
Hi,
When you change the name on the registration, that actually updates the contact record to use the name on the registration.
What you could do in that situation to avoid overwriting the contact is cancel the original registration, and start a new registration with the new information.
|
