Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Events/Attendees/DuplicateWalkinMerge.htm

## Merging Duplicate Walk-in Attendees

End users can merge duplicate walk-in records into existing attendee record. This prevents duplicate attendee records for the same account and ensures data from the walk-in, such as signatures or registration details, is copied to the primary attendee record.

**Who can use this feature?**

* End Users - Browser, iPad
* [Merging Duplicate Walk-In Attendees](#Merging)
* Users require an Events Management License

### Configuring Merging Duplicate Walk-in Attendees for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

To configure this feature:

1. Ensure the following features are configured:

   * [Configuring Events Management](../Configuration/Config.htm)
   * [Reconciling Walk-in Attendees to Existing Accounts](Walk_inAttendees.htm)
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate permission set.
4. Select the **Objects** tab.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | em\_attendee\_\_v | CRED | All | updated\_via\_walkin\_merge\_\_v | Edit |
6. Navigate to the **Application** tab.
7. Grant the following permissions:

   * Access API
   * Merge Records

### Merging Duplicate Walk-In Attendees as

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#)

When end users [reconcile a walk-in attendee](Walk_inAttendees.htm), the matched account\_\_v or user\_\_sys record is checked against existing attendees for the event. If the walk-in attendee is matched to an existing attendee record that does not have a digital signature, a merge confirmation alert displays.

![](../../../Resources/Images/Events/Attendees/MergeDuplicateAttendee.png)

Select Continue to initiate the following merge process:

* Field values from the duplicate record are copied to the existing record, including the following fields:
* em\_attendee\_status\_\_v
* signature\_\_v
* signature\_datetime\_\_v
* meal\_opt\_in\_\_v
* Event registration fields
* Walk-in fields
* The updated\_via\_walkin\_merge\_\_v field on the existing attendee record updates to True, indicating a duplicate record was merged into it
* The duplicate walk-in record is deleted

Users cannot merge a walk-in attendee if the matched existing attendee record has an associated digital signature, as indicated by a populated signature\_datetime\_\_v field.

#### Merged Attendees and Virtual Events

When an attendee record of a [virtual event](../VirtualEvents/HostingVirtualEvents.htm) is merged, the Engage Participant URL from the duplicate walk-in record is transferred to the existing attendee record. If an attendee joins the virtual event using the participant URL from the duplicate walk-in record, post-processing correctly associates the attendance with the existing attendee record.

### Related Topics

[Reconciling Walk-in Attendees to Existing Accounts](Walk_inAttendees.htm)

[Hosting a Virtual Event using Engage](../VirtualEvents/HostingVirtualEvents.htm)