---
title: "March 2025 - Version 5.1"
slug: "march-2025"
tags: ["Events", "Release Notes"]
updated: 2025-04-24T19:02:36Z
published: 2025-04-24T19:02:36Z
canonical: "docs.blackthorn.io/march-2025"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blackthorn.io/llms.txt
> Use this file to discover all available pages before exploring further.

# March 2025 - Version 5.1

Please review the updates below and follow the [upgrade instructions](/v1/docs/march-2025#upgrade-instructions) to upgrade your Events application.

## Table of Contents

- [Breaking Change](/v1/docs/march-2025#breaking-change)
- [Off-Cycle Releases](/v1/docs/march-2025#offcycle-release)
- [BT Salesforce Release](/v1/docs/march-2025#bt-salesforce-release)
- [Webapp Release](/v1/docs/march-2025#webapp-release)
- [Field/Layout Updates](/v1/docs/march-2025#fieldlayout-updates)
- [Upgrade Instructions](/v1/docs/march-2025#upgrade-instructions)
- [Important Definitions](/v1/docs/march-2025#important-definitions)

## Breaking Change

As of the March 5, 2025 Salesforce release, Caching 2.0 will be installed with the upgrade. Please follow the steps below to complete the process.

1. Install the Events app upgrade [using the Candy Shop](https://candyshop.blackthorn.io/products). (If you believe you need to use a direct link, please contact Blackthorn Support. They can provide you with the script and instructions for performing the process manually.)
2. Contact [Blackthorn Support](https://community.blackthorn.io/s/support) to request that the Caching 2.0 installation process be completed. Please include the Org ID for the environment where you want Caching 2.0 enabled.

**Event Group Filters:** When Caching 2.0 is enabled, the **Event Group URL** filters behave differently. The Event Group URL parameters used for filtering Event Groups must not include the **Category** as part of the URL filter, and Event Groups will show up empty.

Please read [Keywords and Event Group Filters](https://docs.blackthorn.io/docs/events-caching-2#keywords-and-event-group-url-filters) for specific information and examples before proceeding.

## Off-Cycle Releases

### March 25, 2025

- If a Form Element contains a picklist value with a colon ( : ), Attendees will see the entire picklist value when selecting an answer. Previously, Attendees only saw the text after the colon. Ex. “Colors: Yellow and Blue” vs. “Yellow and Blue” (Known Issue: 000004540)

### February 25, 2025

- If reCAPTCHA is enabled for a free Event and an Attendee registers for a waitlist-only Event Item, they can complete the registration process. Previously, if the Event Settings **Remove Info Page for Free Events** field was enabled, the registration failed because the user could not respond to the enabled reCAPTCHA on the hidden Payments Info screen. (Known Issue: 000004427)
- If an Event Group contains more than 2000 published and unpublished Events, the Attendee will see the published Events on the **Event Group URL**. Previously, Attendees got the “There are no upcoming events.” error when they clicked the **Event Group URL** because there was a 2000 Events per Event Group limit. (Known Issue: 000004535)

## BT Salesforce Release

*(Release Date: March 18, 2025)*

### Bug Fixes

- **Attendee Record:** When a user registers an Attendee for an Event from the Event record and sets the Attendee’s **Email Opt-in** field to “True” (checked), the **Email Opt-in** field will be checked on the Attendee record. Previously, the **Email Opt-in** field on the Attendee record was not checked. (Known Issue: 000003813)
- **Waitlisting:** When a paid Event has the **UI Experience** set to “Tabbed” and waitlisting is set at the Event level, an Attendee with **Registration Status** set to “Pending” can register for the Event from their AttendeeLink. Previously, Attendees could not register for the Event even though Tickets were available. (Known Issue: 000004422)
- **Duplicate Rules:** Duplicate rules have been updated to ensure completed and processed registrations are handled by duplication logic when configured to block duplicates on creation. Now, duplicate rules will include Event Registration Submission (ERS) records with **Status** set to “To Process” and a value in the new **Primary Email** field. Previously, when duplicate rules were set to block, and a user registered twice while the first ERS record’s **Status** was still set to “To Process,” duplicate records/Invoices were created. (Known Issue: 000004328)
  - Object: Event Registration Submission
    - Field Label: **Primary Email**
    - API Name: conference360__Primary_Email__c
    - Data Type: Email
    - Help Text/Description: “The main email from the event registration. This field is automatically populated.”
  - Permission Set Updates
    - Read\Edit
      - Blackthorn | Events (Organizer)
      - Blackthorn | Events (Admin)
      - Blackthorn | Events (Community/Platform User)
    - Read
      - Blackthorn | Events (Lite User)
      - Blackthorn | Events (Read Only)
      - Blackthorn | Events (Limited Access)
  - New Logic
    - If the Event Settings **Block Duplicate Registrations** = “True” and an Attendee submits a registration that has an ERS record with **Status** set to “To Process” or “Completed” and the **Primary Email** field is populated, then the Attendee will get an error when they try to submit a duplicate registration.
    - If the Event Settings **Block Duplicate Registrations** = “False” and an Attendee submits a registration that has an ERS record with **Status** set to “To Process” or “Completed” and the **Primary Email** field is populated, then the Attendee will be able to submit a duplicate registration successfully.
- **Batch Jobs:** When an Event Organizer uses the EventRevenueRollip batch job after an Event takes place, the job will calculate rollups and update revenue fields as expected. Previously, Event Organizers received the following error message on the EventRevenueRollupBatch job: "First error: Attempt to de-reference a null object." (Known Issue: 000004479)
- **Donations:** When an Event Organizer adds a **Tax Fee** to an Event, Donations (Event Items with **Type** = “Donation”) will automatically be marked as **Tax-Exempt**. They will not be included in tax calculations, whether calculated at checkout or tax-inclusive. Previously, Donations were treated the same as the other Event Items in the cart and were included in any tax calculations.
- **Permissions:** Mobile Check-in app users can change an Attendee’s email address and successfully save the Attendee record. Previously, when a Mobile Check-in app user without read permissions for the Invoice and Lead objects tried to change an Attendee’s email address, they saw the following error. “FATAL_ERROR | System.QueryException: Insufficient permissions: secure query included inaccessible field"
- **Event Groups:** Newly created Events will be assigned to the default Event Group. Previously, new Events were not assigned to the default Event Group if one existed. (Known Issue: 000004514)
- **Event Builder****:** Event Organizers can successfully edit an existing Event with registered Attendees using the Event Builder. Previously, the Event Builder became unresponsive if the Event had registered Attendees and the Session Settings Use Lightning Web Security for Lightning web components and Aura components setting was disabled (unchecked). (Known Issue: 000004344)

#### Email Templates

- When an Event Organizer saves an Email Template created in the Event Builder, the Email Template will be saved as expected. Previously, the Email Template was saved, but an error also occurred.
- When an Event Organizer edits an Event’s Email Template from the Email Template Builder in the Event Builder and saves the edits, they will be returned to the Event they just edited. Previously, if they edited one Event and its Email Template and then a second Event and its Email Template, they were redirected to the first Event after saving the second Event’s Email Template. (Known Issue: 000003373)

#### Form Elements

- When an Attendee searches for a Form Big List Option value with any number of words, the search filter works as expected. Previously, searching for values with three or more words caused the filter to fail. (Known Issue: 000003587)
- When an Event Organizer creates a new or deletes an existing Form Element, saves the changes, and makes additional changes, they will see the Forms Preview automatically update with the latest changes. Previously, the user had to perform a page refresh to see the updates in the “New Form Element” modal.

#### Forms and Mapping

- If a Form that maps Form Submission Answers to fields on an Attendee record is added to the Event’s **Form (Post-Registration)** field and an Attendee completes the Form during registration, the answers will be mapped to the correct fields on the Attendee record. Previously, the answers were not mapped, and there was a mapping error on the Form Submission Answer record. (Known Issue: 000003599)
- When an Attendee uploads a file to answer a pre-registration question (Form Element **Type** = “File Upload”) that is mapped to an image field on the Attendee record, the uploaded file will be stored in Salesforce Files and mapped to the field on the Attendee record. Previously, a BT Log was generated with the “Attempt to de-reference a null object" error, and the file wasn’t uploaded to the correct location. (Known Issue: 000004444)

### Enhancements

- **Recurring Events:** Creating Recurring Events by clicking the **Create Recurring Event** button on the original Event record will also clone the Smart Scheduler scheduled emails (Schedule and Schedule Action records) created from the master template.
- **Scheduled Jobs:** The Blackthorn | Events Attendee Webinar Registration batch job will no longer run when the Schedule Recommended Events Jobs job runs (every hour). The logic contained in the batch job has been placed in other locations, reducing the use of resources.
  - When users view the Zoom registration page for an Event or a Session, they will see the current number of registrants.
  - When a new Attendee registers for the Session or Event, the registrant count will update accordingly.
- **Add to Calendar Feature:** The new **Enable Add Sessions to Calendar** field on the Event Settings object controls whether Attendees can add Sessions as individual calendar entries to their preferred calendar. *Please Note: This field belongs to an upcoming feature and is not functional.*
  - Field Label: **Enable Add Sessions to Calendar**
  - API Name: conference360__ Enable_Add_Sessions_to_Calendar__c
  - Data Type: Checkbox
  - Description: Enables the ability to add individual Sessions as calendar entries when using the Add to Calendar functionality.
  - Help Text: Enable this setting to allow event registrants to add individual Sessions as calendar entries when using the Add to Calendar functionality.

#### Event Builder

- The field sets listed below were updated to include the following fields in each field set’s “Available Fields” section. Event Organizers can now add these fields to the Event Wizard/Event Builder page layouts.
  - Blackthorn | V2 Event Wizard Event Details Section (Blackthorn | Event Builder Event Details Section)
    - **Free** (Event.Free__c)
    - **Post Registration** (Event.After_Submission__c)
    - **Redirect URL** (Event.Registration_Redirect_URL__c)
    - **Registration Success Message** (Event.Success_Message__c)
    - **Automated Email From Address** (Event.Automated_Email_From_Address__c)
    - **Confirmation Email** (Event.Confirmation_Email__c)
    - **Waitlisted Email** (Event.Waitlisted_Email__c)
    - **Waitlisted Pending Email** (Event.Waitlisted_Pending_Email__c)
  - Blackthorn | V2 Event Wizard Organizer Section (Blackthorn | Event Builder Organizer Section)
    - **Organizer (Contact)** (Event.Organizer_Contact__c)
  - Blackthorn | Event Builder Session Fields
    - **Description** (Session.Description__c)
  - Blackthorn | V2 Event Wizard Virtual Section (Blackthorn | Event Builder Virtual Section)
    - **Zoom Registration Approval Type** (Event.Zoom_Registration_Approval_Type__c)
    - **Include Zoom URL In Calendar Description** (Event.Include_Zoom_URL_In_Calendar_Description__c)
    - **Zoom Email Notifications** (Event.Zoom_Email_Notifications__c)
    - **Zoom Personal Meeting ID Enabled** (Event.Zoom_Personal_Meeting_ID_Enabled__c)
    - **Webinar/Meeting ID** (Event.Webinar_ID__c)
- The Event Builder’s FAQ section now includes an **Enable Rich Text** toggle. Event Organizers can use the toggle to switch between regular text and rich text when entering an **Answer** in the Event Builder.
- The Email section of the Event Builder now includes additional guidance, including updated help text and visual cues, to help Event Organizers use the component.
- When editing an existing **Question** in the Event Builder’s FAQ section, the Event Organizer will only see the question they are editing. The existing question list and the “create a new question” component will be hidden. Once the Event Organizer clicks **Save** or cancels the edit, they will see the list of existing questions and the “create a new question” component.
- Event Organizers can now add an Event FAQ **Category** from within the Event Builder.
  - If the **Category** field is populated, the question will be listed under that expandable category.
  - If the **Category** field is blank, the question will be listed with the uncategorized questions.

## Webapp Release

*(Release Date: March 18, 2025)*

### Bug Fixes

- **Translations:** Attendees will see the Speakers tab on the Event webpage translated to Dutch when an Event with the Tabbed UI has an Event Settings record with **Source Language** = “Dutch” and **Target Language** = “English.” Previously, everything but the Speakers tab was translated into Dutch. (Known Issue: 000003491)
- **Experience Cloud:** An Experience Cloud user who has already registered for an Event cannot use the **Add Myself** button to register for the Event a second time. When using the Tabbed or Dynamic UI, the **Add Myself** button will be disabled after the first registration. Previously, users could click the **Add Myself** button and try to register a second time. (Known Issue: 000003442)
- **Data Dictionary:** If an Event using the Data Dictionary has a Data Dictionary Entry with the **Key** set to “MSG_ATTLINK_CONFIRM_REGISTERED” and text in the **Value** field, then an Attendee will see the full text from the **Value** field when they click their AttendeeLink. Previously, the last character in the **Value** field’s text was deleted. (Known Issue: 000004403)
- **Forms:** When an Event Item has a Form with a required multi-select picklist question (Form Element), Attendees must answer the question to continue the checkout process. Previously, removing a different Ticket from the cart allowed Attendees to complete their registration without answering the required multi-select picklist question.

#### Event Records

- Clicking the **Update** button on a published Event record will populate both the **Last Publish To Platform Completed At** and **Last Publish To Platform Requested At** fields. Previously, the Event’s **Last Publish To Platform Completed At** field was not populated after the Event Organizer clicked the **Update** button. (Known Issue: 000003686)
- Events with the **UI Experience** set to “Dynamic” will now show the Event's **Venue City**, **Venue State/Province**, and **Venue Country**. Previously, Attendees only saw the **Venue City** and **Venue State/Province**, which caused confusion since there are multiple states with cities of the same name.
- If an Event uses a post-registration **Redirect URL** with the Dynamic UI and a “re-direct checkout” platform such as Stripe Checkout, TouchNet, or Transact (CashNet), the Attendee will be directed to the correct URL after they complete the registration process. Previously, the Attendee was directed to the registration success page instead of the **Redirect URL**.

#### Registration Experience

- When an Attendee registers for an Event, they can navigate back and forth between pages without encountering a blank screen. Previously, when an Attendee clicked **Next**, then clicked **Back** to revisit the Ticket selection page, and clicked **Next** again, they were taken to a blank screen. (Known Issue: 000003418)
- Removing a Ticket from the Summary screen by clicking the “X” returns the Attendee to the Ticket Quantity Selection page instead of showing a blank screen.

### Enhancements

- **Event Images:** If an Event has the **UI Experience** set to “Dynamic” and an Event Organizer enters a value in an Event’s **Thumbnail and Mobile Image URL** image field, Attendees will see the image when using a mobile browser. If the Event’s **Thumbnail and Mobile Image URL** field is blank, Attendees will see the banner image in the Event’s **Image URL** field.
- **Checkout Process:** If an Event registrant misses a required field on the Contact or Payment Info forms or enters incorrect data, they will see an error summary at the top of the page. The error summary will include links that direct the individual’s focus to the field(s) with the errors. Screen readers can also access and read the error summary, improving accessibility.
- **reCAPTCHA:** If a free Event has the Event Settings **Remove Info Page for Free Events** and **Enable Captcha** fields enabled, Attendees will see the reCAPTCHA on the last page of the registration process.
- **Search an Event:** If the Event Settings **Search Bar** field is set to “On,” Attendees can search the Event for related information using the following search criteria.
  - Sponsors: **Display Name**
  - Speakers: **First Name** and **Last Name**
  - Attendees: **First Name**, **Last Name**, and **Title**
  - Sessions: **Session Name**
  - Event FAQ:
    - existing questions: **Question** in simple or richTextQuestion form and **Answer** in simple or richTextAnswer form
    - new questions: **Question** in simpleTextQuestion form and **Answer** in simpleTextAnswer form

#### FAQ Component

- When an Event’s **UI Experience** is set to “Dynamic” and an Attendee reads the FAQ section on an Event’s webpage, they will see an **Expand All/Collapse All** button. Clicking the button will expand or collapse all the FAQ questions with a single click.
- The user interface for the FAQ component was updated to improve accessibility and the visual structure of the questions.
  - The Event FAQ’s **Question** field now uses a simple text format to ensure it is displayed correctly.
  - The Event FAQ’s **Answer** field is still a rich text field.
  - The Frequently Asked Questions section of an Event's website will respect the branding (colors, font, etc.) set in the Event Settings record.
  - Event FAQ questions with a blank **Category** field (uncategorized questions) will be grouped in their own section without a section title.
  - Event FAQ questions with a value in the **Category** field will have the **Category** as the section title instead of “Expand [**Category**] Questions.“
  - When an Attendee toggles open an individual question, the answer will be visible. However, Attendees will no longer see all the questions and answers when they open a section.

## Field/Layout Updates

### New

- Object: Event Registration Submission
  - Field Label: **Primary Email**
  - API Name: conference360__Primary_Email__c
  - Data Type: Email
  - Help Text/Description: “The main email from the event registration. This field is automatically populated.”
- Object: Event Settings *(This field belongs to an upcoming feature and is not functional.)*
  - Field Label: **Enable Add Sessions to Calendar**
  - API Name: conference360__ Enable_Add_Sessions_to_Calendar__c
  - Data Type: Checkbox
  - Description: Enables the ability to add individual Sessions as calendar entries when using the Add to Calendar functionality.
  - Help Text: Enable this setting to allow event registrants to add individual Sessions as calendar entries when using the Add to Calendar functionality.

## Upgrade Instructions

Go to the [Blackthorn Candy Shop](https://candyshop.blackthorn.io/products) to upgrade Events to the newest version.

Blackthorn has adopted Salesforce’s managed package installer to simplify the installation process. The installer will confirm that the correct Base Package and Payments versions are installed before upgrading Events.

For step-by-step instructions, click [here](https://docs.blackthorn.io/docs/blackthorn-events-installation).

## Important Definitions

### Breaking Change

A breaking change is a significant change that requires a package upgrade to see the update.

### Off-Cycle or Hotfix Release

A hotfix is a release that corrects a problem that impacted extensive functionality.

### BT Salesforce Release

The following applies to a Salesforce release.

- Salesforce fixes REQUIRE a package upgrade to see and utilize the fixes/enhancements.
- Only users with a System Administrator profile or the ModifyAllData system permission can install packages.

### Webapp Release

The following applies to a Webapp Release (previously referred to as a platform release).

- Webapp fixes/changes usually do not require updates to the Salesforce package.
- These updates automatically apply to all customers; you cannot opt-out.

**If you have any questions or need help with testing, please contact [Blackthorn Support](https://community.blackthorn.io/s/support).**