Added the ability to filter contacts by department and sub-department fields, allowing you to more easily segment and search your contact database.

Minor visual update to the Event Setup Assistant function inventory control toggle.

Agenda Widget: Removed the "Speaker" label from speaker cards within the Agenda widget to provide a cleaner visual layout for site visitors.
​

Agenda Widget: Updated the background colors and removed border shadows in the Agenda details screen for presentations, session roles, and handouts to improve visual clarity for site visitors.

Improved the way uploaded or dropped-in images are saved from the HTML editor, to get smaller file sizes and faster load times for emails, app and website content.

When you've set up the Function to create linked contact records, you can now choose which guest fields (Last Name, Organization, or Email) are required, rather than having to collect all three. [In the Details tab for that function, in the Interactive Site builder.] A validation check and guidance message have been added to ensure at least one of these fields is marked as required to allow for successful contact creation.
​

Duplicate invoices were created if the save button was clicked multiple times in quick succession within Supplier Invoice Management. [Ref: AE-1871]

Application Setup - Users: The inactive date was not cleared when a user was reactivated, causing the previous date to be retained if the user was made inactive again. [Ref: AE-1869]

App PINs and access tokens were cleared from event-level contact records if the linked record in the Contact Store was deleted. [Ref: AE-1866]

Exhibition stands and sponsorship packages weren’t automatically cancelled or released back into inventory when the associated booking contact record was deleted. [Ref: AE-1873]

When filtering attendees, excluding contacts with no registration would sometimes time out in events with several thousand records. [Ref: AE-1910]

Newly uploaded contact custom fields (document-type) in a Contact Store record could become empty if the event-level contact record was edited and saved in quick succession (before the assets had fully loaded in the background). [Ref: AE-969]

Tax was incorrectly applied to canceled registration items if the tax configuration was updated in the setup after the item had been added to a contact record. [Ref: AE-1942]

Function registrations could be missing corresponding guest data if the function setting ‘Guest names do not need to be recorded’ was changed to ‘Create a new linked contact record’ after registrations had already been processed. [Ref: AE-1885]

Attendee Financials: Total amounts could display "NaN" instead of 0.00 when multiple items with discount codes applied resulted in a zero balance. [Ref: AE-1935]

Attendee Financials: Refunds sometimes wouldn’t save correctly in EventsAir and displayed a null reference error, even though they were successfully processed in the Stripe payment gateway, if an older API key was being referenced. [Ref: AE-1909]

Attendee Financials: Refunds that received a 'pending' response from a payment gateway weren't recorded as successful in EventsAir, even if they were processed correctly by the gateway. [Ref: PE-2383]

Interactive site links inserted into Contact Store merge documents would sometimes reference the incorrect event if the site had been cloned from another event linked to the same Contact Store. [Ref: AE-1906]

Merging contacts would occasionally result in a SQL error and not complete, if both contacts had profile photos and the main contact was linked to other events. [Ref: AE-1899]
​

When merging an inactive contact into an active contact, the resulting record would sometimes become inactive even if the active record was selected as the main contact. [Ref: AE-1907]

Dietary requirements wouldn't update or clear correctly when using the Import Data express action. [Ref: AE-1868]
​

Imports containing more than 500 rows would load indefinitely and not display a completion message, even if some records were processed successfully. [Ref: AE-1965]
​

Imports were experiencing performance delays when duplicate checking was enabled, as the system was unnecessarily loading full contact photo files during the matching process. [Ref: PE-2301]

The "estimated time of arrival" field for accommodation wouldn't become editable unless the "estimated time of departure" field was also enabled. [Ref: PE-2325]

The Attendee Summary report and other financial reports wouldn't load in the preview viewer when running on large, unfiltered datasets. [Ref: AE-1952]
​

The ‘Details’ column in the Attendee Payment Details List and Payment Detail List reports appeared empty (or on a second line) when exported to CSV, when Multiline was set to true. [Ref: PE-2322]
​

The Global Payment List report wouldn’t load and gave ‘Internal Server Error’ when using the preview viewer. [Ref: PE-2391]

Accommodation Setup: The date range for room inventory couldn’t be extended if the room had a dynamic rate and multi-currency was enabled. [Ref: AE-1874]

Packages Setup: Timestamps were incorrectly added to accommodation or travel dates within packages if you were using a device with a different Daylight Saving Time status than the selected date. [Ref: AE-1900]

Financial Setup: Direct deposit payment types wouldn’t save if the fee type was set to a fixed amount (the system incorrectly required the value to be a percentage). [Ref: AE-1946]

Name Badge Setup: Name badges wouldn't load or open for editing if a calculated field had been added during the initial creation and save of the badge. [Ref: AE-1955]

Functions Setup: Planners could not block all unallocated seats on a table at once during function table allocation [they could only block one seat at a time]. [Ref: PE-2361]

Images in the Attendee App and event websites, such as speaker photos and exhibitor logos, intermittently didn't display correctly if they were high-resolution files. [Ref: PE-2329]
​

Duplicate presentation documents could be created for the same document type, which prevented the resource gallery in the Attendee App and the OnAIR portal from updating correctly. [Ref: AE-1829]
​

Vimeo Video on Demand sessions wouldn't play in both the Attendee App and OnAIR portal simultaneously, as the Attendee App only supported video IDs while the OnAIR portal only supported full URLs. [Ref: AE-1923]

The Attendee App builder wouldn't open or save correctly if it referenced images or assets that had been deleted. [Ref: AE-1894]
​

If the event name was intentionally removed in the Modern Attendee App builder Style settings tab, the name was automatically re-added when the app builder was reopened. [Ref: AE-1768]
​

If an Attendee App had too many banner images, sometimes the builder couldn't be saved and a "content too large" error was displayed. [Ref: AE-1832]

Portal authentication filters were bypassed when a portal user accessed a site using an auto-login token, allowing unauthorized contacts to access restricted portals. [Ref: AE-1917]
​

The “Is Disabled” checkbox in the Users tab of portal apps now remains selected after saving and reopening the portal, ensuring the user account status is accurately reflected. [Ref: AE-1931]

Uploaded custom field documents weren't saved if "Allow Abstract Editing" was enabled and the document was uploaded via the additional information section. [Ref: AE-1949]
​

The author list in printed abstracts was re-ordered alphabetically instead of maintaining the original submission order. [Ref: AE-1950]
​

Sorting by the Weighted Score column on the Abstracts page caused pagination to break and only displayed the first 100 records if the total dataset exceeded that amount. [Ref: AE-1948]

Privacy options for co-author records created through the portal were defaulting to null instead of "no privacy recorded". [Ref: PE-2324]

The portal wouldn’t load for exhibitors if lead scanning was enabled but the navigation headings for Lead Management were left empty. [Ref: AE-1958]
​

Several shapes added to the floor plan editor, such as gears and batteries, didn't display correctly on the live floor plan. [Ref: PE-2330]
​

The country code drop-down for phone number fields didn't display correctly when an interactive form was embedded in the portal. [Ref: PE-2390]

Site visitors were not redirected to the badge print page after completing a payment via EventsAir Pay (Stripe), requiring a manual reset of the kiosk. [Ref: AE-1932]

Exhibitors didn't display in the exhibitor search if the ‘combine exhibitor and co-exhibitor’ setting was enabled and any exhibitor had a stand type booking without a stand number. [Ref: AE-1956]

The "Confirm and Export Selected Bookings" button wouldn't download the export file if the event was set to certain time zones (more common with time zones on the half hour, eg GMT+10.5). [Ref: PE-2328]

The Available Financial Report list contained duplicate entries for Invoices, Miscellaneous Invoices, and Receipts. [Ref: PE-2331]

The abstract book wouldn't export if uploaded .docx files contained specific tracked formatting changes. [Ref: AE-1957]
​

Exporting the abstract book with extremely large document data would time out when multiple paper statuses were selected simultaneously. [Ref: PE-2326]

The audio in pre-recorded media could sometimes become out of sync with the video during live broadcasts or session recordings when the host's computer was under heavy system load. [Ref: AE-1924]

Live Support: The notification sound didn't play when a new live support request was received in the OnAIR portal. [Ref: AE-1951]
​

The OnAIR portal builder would sometimes not open if certain true/false settings were saved incorrectly as empty values. [Ref: AE-1893]
​

The live host broadcast feed appeared choppy for attendees, particularly when the host's computer was under heavy load or using a lower frame rate. [Ref: AE-1928]
​

The timeline wouldn't load and displayed a continuous spinner after login if duplicate portal assets were present. [Ref: AE-1892]

Online Panel - Live Q&A portal: OnAir live Q&A tabs stacked vertically instead of displaying horizontally if the parent portal's brand was changed or deleted. [Ref: AE-1891]

Modern event websites with a large number of pages would sometimes not clone successfully. [Ref: PE-2408]

Agenda preview (in the builder): Session roles in the agenda widget preview didn't display the contact's photo, position, or organization if no speakers were attached to the session. [Ref: PE-2379]
​

Agenda widget: Session overview and details were truncated without a "Show More" option when opened directly by a site visitor [it worked when navigating between sessions]. [Ref: PE-2377]
​

Agenda widget: Attendees assigned as role and a speaker for the same session only displayed as a speaker. [Ref: PE-2410]
​

Agenda widget: Session times were displaying incorrectly and merging AM and PM sessions when the browser language was set to Portuguese or Dutch. [Ref: PE-2358]

(Modern theme) Organization and Billing Organization fields were auto-correcting to title-casing. [Ref: AE-1889]
​

(Modern theme) The country code drop-down for the Mobile field didn't display correctly or displayed blank when it expanded upward. Additionally, unnecessary blank space was appearing when the drop-down expanded downward. [Ref: AE-1898]

(Modern theme) Some banner images appeared cut off in mobile and desktop in Full Page Layout mode. [Ref: AE-1849]
​

Registration totals didn’t display correctly if the same payable item was included on multiple pages within the site. [Ref: AE-1756]

(Modern theme) Site visitors using an auto-login token to sign in were shown a blank page if the ‘Token users are required to create an account’ option was disabled. [Ref: AE-1904]

An indefinite loading screen would display if display logic was applied to a function fee type with a number input and a minimum value of 1. [Ref: AE-1782]
​

Sites wouldn't load if a text part within a contact component contained invalid logic data. [Ref: AE-1795]
​

Pre-existing interactive sites would malfunction if the event's base currency was changed, such as incorrectly displaying items as "Full", asking them to “select a radio button” when one doesn’t show on the page, or preventing site visitors from completing their registration. [Ref: AE-1858]
​

Page display logic didn't work correctly for group members when page logic was applied to a group component. [Ref: AE-1915]

The group contact component didn't respect read-only editability settings if the "Add ‘I am not attending’ option" was enabled. [Ref: AE-1803]

Accommodation discount codes could be overbooked if a site visitor made multiple bookings within the same session. [Ref: AE-1888]
​

A rounding difference could cause a 0.01 balance to appear as outstanding when specific combinations of exchange rates and discount codes were used during online payments. [Ref: AE-1857]

The app would hang indefinitely during login if a Function Check-In component had an interactive site attached. [Ref: AE-1925]
​

App users were unable to log in and remained on a loading screen if the app's font was set to Arial, Times New Roman, or Roboto. [Ref: AE-1927]
​

App users were intermittently unable to progress past the login screen if the app had been cloned from another event. [Ref: AE-1930]
​

Attendees who were not registered for a function could not be scanned in, even when the "Restrict access to registered function attendees only" setting was disabled. [Ref: AE-1926]

Updating an event-level custom field via the GraphQL API would incorrectly clear the event's email account, event format, and expected attendee settings. [Ref: AE-1941]