Clone
  • 11 Nov 2024
  • 3 Minutes to read
  • Dark
    Light

Clone

  • Dark
    Light

Article summary

Update Your New Event's Total Capacity

Users must manually update a cloned Event’s Total Capacity after cloning an Event because cloning an Event resets the new Event's Total Capacity to the cloned Event Item’s Quantity Available.

Need to duplicate your Event quickly with all of the related information like Attendees, Event Items, Sessions, Sponsors, Form Elements, etc? Now you can, in three simple steps with our Clone feature!

Before You Clone

Permissions

A standard user must have one of the following permission sets to be able to clone Event records.

  • Blackthorn | Events (Admin)
  • Blackthorn | Events (Organizer)
  • Blackthorn | Events (Community/Platform User)

Page Layout

Standard Users' Page Layout

When cloning an Event, standard users will use the default page layout, which includes any Related Lists that may have been removed on the original Event record.

The Deep Clone Layout now includes the following fields: Confirmation Email, Waitlisted Email, and Waitlisted Pending Email. Previously, only the Email Template Related List was cloned.

Installations after March 2024 will include the fields on the Deep Clone Layout; however, existing customers must manually add the fields. Follow the steps below to add the custom fields to the Event Deep Clone Layout.

  1. Click the Gear icon.
  2. Click Setup.
  3. Click the Object Manager tab.
  4. In the Quick Find box, enter and click "Event" (conference360__Event__c).
  5. Click the Field Sets tab.
  6. Click “Deep Clone Layout."
  7. Drag and drop the following fields in the "In the Field Set" list.
    • Confirmation Email (conference360__Confirmation_Email__c)
    • Waitlisted Email (conference360__Waitlisted_Email__c)
    • Waitlisted Pending Email (conference360__Waitlisted_Pending_Email__c)
  8. To make a field required, hover over the field in the "In the Field Set" box, click the Wrench icon, and check the Required checkbox.
  9. Click OK.
  10. Click Save.

Finally, confirm that any other fields you want to clone are on our Deep Clone field set.

Clone Field Sets

Classic/Lightning

  1. Go to the Event record and click the Clone button. To select all objects at one time, click the Clone All button.
    Click Clone Button

  2. Select the Related Items.
    The right side of your screen will display a list of all related items. Toggle the Clone button to select which Related List should also be cloned. Leaving them gray will not clone the Related List.

    • Example: If I wanted to clone the "Speakers" Related List to my new Event, I would toggle "Active".
    • Example: If I didn't want to clone the "Staff" Related List, I would leave it as "Inactive".
      Choose what to clone
  3. Click the Clone button.
    Once you click the Clone button, a new Event will be created.

Custom Questions (Form) Clone

To deep clone forms in lightning experience:

  1. Edit the Form page layout.
  2. Add the custom Clone button from the previous Mobile/Lightning actions.
    Custom Questions Form
  3. Select the Form to be cloned. Click the Clone button. The Form and accompanying questions are cloned.
    Form Click Clone

Add a Custom Field to the Clone Feature

Lightning

  1. Create a custom field (Random Field) on the Event object.
    Create Custom Field on Event Object

  2. Edit the field set within the Event object and add the custom field (Random Field).
    Edit Field Set

  3. Save the Event object and clone the Event. You can now see the custom field (Random Field) is ready to be cloned.
    Custom Field Ready to be Cloned

Cloning with Sessions

When cloning an Event with Sessions in it, the Start Date, Start Time, End Date, and End Time of the cloned Sessions will automatically be reset and need to be filled in again.

Cloning with Fees

Cloning an existing Event with a Payment Processing Fee will result in a cloned Event that includes the same Payment Processing Fee value.

  • If the original Event's Payment Processing Fee field is blank, the cloned Event's Payment Processing Fee will also be blank.
  • If a Default Fee value exists on the original Event, the cloned Event will have the Default Fee related to it.

The Payment Processing Fee related to the Event that is being cloned takes priority over the Default Fee, including empty fields.


What's Next