May 2026 - Version 5.47
(Release Date: June 2, 2026)
Table of Contents
📋 At a glance
This month brings AttendeeLink self-service contact updates, so your registered attendees can update their own details post registration, and we've added an Authorize.Net hosted checkout option for events using that gateway. There's also new Fair Market Value (FMV) tracking for tax receipts and a ready-made set of event ROI reports and dashboards. We've also fixed a handful of registration, checkout, and embedded-iframe issues.
| Update | What it does | For whom | Setup |
|---|---|---|---|
| 👤 AttendeeLink self-service updates | Attendees update their own contact details on AttendeeLink | Organizers · Attendees | 📦 Events 5.47 |
| 🧾 Fair Market Value tracking | Tax-deductible value across items, invoices & transactions | Organizers · Finance | 📦 Events 5.47 |
| 📊 Event ROI reports & dashboards | Out-of-the-box performance reporting + analytics cards | Organizers · Leadership | 📦 Events 5.47 |
| 💳 Authorize.Net hosted checkout | Optional hosted card form (narrows PCI scope) | Admins | 📦 Events 5.47 |
| 🐛 Registration, checkout & webpage fixes | Apostrophe emails, waitlist, 11th attendee, embedded sizing, and more | Everyone | Mixed (some auto) |
Some changes ship in the Events 5.47 Salesforce package and need to be installed by an admin; others ship automatically in our May webapp release and are already live for everyone. Each item below is tagged so you can tell which is which.
⚠️ Action required
Installing packages manually? Install Payments 6.60 before Events 5.47.
Events 5.47 uses a new setting that's added in Payments 6.60, so Payments needs to come first. If you upgrade through the Candy Shop, this is handled for you automatically.
✨ What's new
Items tagged Salesforce upgrade required are part of the Events 5.47 package (or Payments 6.60, where a change uses a Payments-side setting) and need to be installed by an admin. Items without a tag are already live for everyone — they shipped automatically in our May webapp release.
🛒 Registration & checkout
AttendeeLink self-service contact updates (Salesforce upgrade required)
Save your team time on the routine update requests. Your registered attendees can now update their own contact details right from their personal AttendeeLink, instead of emailing your team for help. You decide per event whether to offer this, which fields attendees can change, and how close to the event the edit window stays open. You can let attendees edit any combination of these fields:
- First Name
- Last Name
- Company
- Phone
- Title
- Address
- Country
- Salutation
- Dietary Preference
- Custom Questions
Whatever you leave out stays read-only, and if you don't enable any fields, the page stays view-only. Every successful change is logged on the Attendee record, so you have a clear audit trail.
Known limitation:
The new self-service update endpoint does NOT enforce the "One Unique Email per Event" rule. If you allow email as an editable field, an attendee could change their email to one already used on the same event and the system will not block the change. To prevent this in the short term, do not include "Email" in the Editable AttendeeLink Fields picklist. This gap will be closed in a future release.
📊 Reporting & analytics
Fair Market Value (FMV) tracking for tax receipts (Salesforce upgrade required)
If you need to tell attendees or donors how much of a payment is tax-deductible, you can now track Fair Market Value right on your Event Items. On each Event Item, set either an FMV % of the ticket price or a flat FMV Amount. From there, Blackthorn does the rest: it calculates the FMV for each line item, totals it on the Sales Document, and mirrors that total onto the Transaction, so the value is ready for your receipts and reporting. Set FMV on the Event Items where it applies, and leave it blank everywhere else.
Event ROI reports and dashboards (Salesforce upgrade required)
This release adds a ready-made reporting and dashboards package for measuring event performance. On your Event and Event Group record pages, you'll now see built-in analytics cards, including year-over-year comparisons and an Event Group performance view. A new Blackthorn | Events ROI folder gives you reports across planning, finance, and marketing, plus matching Planning, Finance, and Marketing dashboards. To keep year-over-year and trend views fast, Blackthorn captures a daily snapshot of each event's key numbers automatically in the background. To give your team access, assign the new Blackthorn | Events (Reporting) permission set.
Authorize.Net hosted checkout (Salesforce upgrade required)
If you process payments through Authorize.Net, you can now switch your gateway to a hosted checkout mode. Previously, attendees typed their card details into fields on the Blackthorn checkout page, and those details were sent directly to Authorize.Net from the browser. With the new mode, the entire card form is served by Authorize.Net inside a secure embedded frame, so card details are never entered on a Blackthorn page at all, and your checkout only ever receives a transaction reference back. This narrows the part of your checkout that's in scope for PCI, which can simplify your SAQ A compliance. Your admin turns this on per Payment Gateway record.
🐛 What's fixed
Items tagged Salesforce upgrade required are part of the Events 5.47 package and need to be installed by an admin. Items without a tag are already live for everyone — they shipped automatically in our May webapp release.
🛒 Registration & checkout
- Picking a different ticket after canceling checkout: Previously, if a logged-in attendee on a Community or Experience Cloud page started checkout, canceled, and tried to pick a different ticket, the ticket buttons stopped working — they had to refresh the page to recover. Now they can simply pick a different ticket and continue. (Known Issue: 000005344)
- "Wait list capacity reached" error during checkout (Salesforce upgrade required): Previously, when an attendee's cart happened to fill the exact last spots of a waitlist-enabled event item, they saw a confusing "Wait list capacity reached: Please remove it from your cart to complete registration" error and couldn't finish registering — even though there was actually room. Now the checkout completes correctly.
- Registration for attendees with an apostrophe in their email (Salesforce upgrade required): Previously, an attendee with an apostrophe in their email address (like
j.o'connell@example.com) couldn't register if your event had "One Unique Email per Event" or "Block Duplicate Registrations" turned on. Now their registration goes through without any issue. (Known Issue: 000004191) - 11th attendee on Navigator-enabled events (Salesforce upgrade required): Previously, the 11th person trying to register for an event with the Blackthorn Navigator app enabled hit an internal Salesforce limit and the registration failed, effectively capping the event at 10 registrations. Now registrations continue past 10 with no issue.
🔒 Invite-only events
- Invited attendees can no longer create duplicate registrations through AttendeeLink (Salesforce upgrade required): Previously, when "One Unique Email per Event" was turned on, your invited attendees could still register a second time through their AttendeeLink using a duplicate email — creating duplicate Attendee and Session Attendee records that someone on your team had to clean up. Now the duplicate-email rule blocks this for invited attendees too. (Known Issue: 000005244)
- "Done" and "Contact Support" buttons on AttendeeLink: Previously, the "Done" and "Contact Support" buttons on the AttendeeLink check-in page weren't working — clicking either button after registration didn't go anywhere. Now they navigate as expected.
🌐 Event webpage
- Embedded events no longer collapse to a thin strip: Previously, when you embedded a Dynamic UI event in an iframe on your own page, the embedded area could shrink to almost nothing after the attendee clicked Get Tickets — leaving them looking at a tiny sliver with no way to see tickets or complete checkout. Now the embedded event keeps its full size correctly. (Known Issue: 000005401)
- Section dividers on Dynamic UI event pages: Previously, on the Dynamic UI event page, the dividers between sections like Speakers, Sessions, Tickets, and FAQs ran the full width of the page while the content inside stayed centered, which made the page look lopsided at wider screen sizes. Now the dividers line up neatly with the centered content.
- Checkout payment-error message styling: Previously, error messages on the checkout payment step displayed with styling that didn't match other errors on the page. Now they look consistent with the rest of the checkout's error styling.
- Dropdown menu and language-selector backgrounds: Previously, dropdown menus and the language-selector were showing as transparent in some event themes, which made menu items hard to read against the page behind them. Now they have solid backgrounds.
- Mobile language-selector backdrop: Previously, when an attendee opened the language selector on a mobile device, the page content behind it showed through the backdrop. Now the backdrop is a solid color.
- Order confirmation page formatting: Previously, on the order confirmation page, bold text and bullet points in your event descriptions weren't rendering correctly, and spacing was uneven across the order summary, checkout stepper, payment form, and divider elements. Now everything renders cleanly.
⏰ Smart Scheduler
- Sending email from an Attendee record with SendGrid and an org-wide address (Salesforce upgrade required): Previously, if you tried to send an email from an Attendee record and your org was using both SendGrid and an org-wide email address, the send would fail with "Send email failed. You have uncommitted work pending. Please commit or rollback before calling out." Now the email sends correctly.
🛠️ Technical reference
This section is intended for Salesforce admins. Field API names, permission set details, and configuration notes are grouped by the feature they relate to.
AttendeeLink self-service contact updates — fields
- Event Settings · Allow AttendeeLink Self-Service Edit —
conference360__Allow_AttendeeLink_Self_Service_Edit__c— Checkbox, default unchecked. Allow attendees to self-service edit their contact info on the AttendeeLink check-in page after registration. Read/Edit: Events (Admin), (Organizer); Read Only: (Limited Access), (Lite User), (Community Platform User), (Read Only). - Event Settings · AttendeeLink Self-Service Cutoff Date —
conference360__AttendeeLink_Self_Service_Cutoff_Date__c— DateTime. Default: none (falls back to Event Start Date; if blank, editing is unrestricted). Attendees cannot edit on or after this date/time. Read/Edit: Events (Admin), (Organizer); Read Only: the rest. - Event Settings · Editable AttendeeLink Fields —
conference360__Editable_AttendeeLink_Fields__c— Multiselect Picklist (First Name, Last Name, Email, Company, Phone, Title, Address, Country, Salutation, Dietary Preference, Custom Questions). Default: none selected. Leave blank to disallow all edits, even when self-service is enabled. Read/Edit: Events (Admin), (Organizer). - Attendee · AttendeeLink Self-Service Edit Log —
conference360__AttendeeLink_Self_Service_Edit_Log__c— Long Text Area (32,768). Audit log of attendee self-service contact edits, prepended by the system on each successful update. Read/Edit: Events (Admin) only.
Fair Market Value (FMV) tracking — fields, rules & reports
How it works: When an Event Item has an FMV % or FMV Amount set, the package computes a per-unit FMV, multiplies it by line quantity onto each related Line Item, sums those to the parent Sales Document, and copies the Sales Document total onto related Transactions. Event Items with no FMV configured are skipped. Set either FMV % or FMV Amount, not both; for FMV %, enter a whole percent (e.g. 20) or a decimal (0.20) — values ≥1 are divided by 100.
- Event Item: FMV %
FMV_Percent__cNumber(6,4) input · FMV AmountFMV_Amount__cCurrency(18,2) input · FMV ComputedFMV_Computed__cCurrency(18,2) system-managed - Line Item (
bt_stripe__Line_Item__c): FMV AmountFMV_Computed__cCurrency(18,2) — per-unit FMV × quantity - Sales Document (
bt_stripe__Sales_Document__c): FMV TotalFMV_Total__cCurrency(18,2) — sum of line FMV - Transaction (
bt_stripe__Transaction__c): FMV TotalFMV_Total__cCurrency(18,2) — copied from the Sales Document
Permission sets: FMV % and FMV Amount editable for Events (Admin), (Organizer), (Community Platform User); read-only for (Lite User), (Limited Access), (Read Only). All computed/total fields read-only everywhere.
Validation rule: "Provide either FMV % or FMV Amount, not both" on the Event Item.
Reports: FMV by Ticket Type, FMV by Sales Document, FMV by Transaction (in the Blackthorn | Events ROI folder).
Event ROI reporting and dashboards — object, permission set & components
- New object: Event Daily Snapshot (
Event_Daily_Snapshot__c) — stores a daily point-in-time snapshot of event metrics for year-over-year and trend reports; created automatically by a scheduled batch. - New permission set: Blackthorn | Events (Reporting) — grants Run Reports, access to the snapshot object and analytics fields, and the reporting Apex classes.
- Record-page components: the packaged Event record page adds a year-over-year report card + analytics reports component; the Event Group page adds an Event Group performance dashboard action.
- Reports & dashboards: a new Blackthorn | Events ROI report folder + dashboard folder (planning, finance, marketing).
- Configuration: report behavior is driven by the
BT_Report_Definition__mdtCustom Metadata Type. Most orgs won't need to change these.
Authorize.Net hosted checkout — how it works & setup
Under the hood: the previous Authorize.Net flow rendered card fields on the Blackthorn checkout page and tokenized in the browser (accept.js). The new mode uses Authorize.Net's Accept Hosted iframe: the card form is served entirely by Authorize.Net, card data never enters a Blackthorn page or DOM, and the checkout receives only a transaction reference back — removing the Blackthorn page from the card-data path.
Setup: check the SAQ-A Mode field on the relevant Payment Gateway record. This field is added by Payments 6.60 — see the Payments release notes for the full field definition and the bt_stripe__AcceptHosted_Settings__mdt Custom Metadata Type that ships alongside it. Most orgs won't need to change the Communicator URL defaults.
⬆️ How to upgrade
Go to the Blackthorn Candy Shop to upgrade Events to 5.47. Upgrade Payments to 6.60 first (see Action required above).
For step-by-step instructions, click here.