EleventWhat's new
← All updates
New FeatureImprovementElevent for Salesforce

Elevent for Salesforce v2.4

With this update from v2.3 to v2.4, we've introducing a set of improvements to improve the data sync, adding some small features, and bringing in ticket data as product types. Along with the usual set of bug fixes.

New option: Don't Import Entries

Entries, often called check-ins or scans, can be a ton of data. In an org like Salesforce, where data usage is very limited, it can mount up to a lot of data usage you don't value.

If you aren't planning to use the data about each person's actual attendance, you can check a box in the Elevent Custom Setting to "Skip Entries Import".

image.png

Ticket Products are Now Imported

In Salesforce, the app creates unique products for every other type of item but tickets--these are the 'SKUs' of your product mix.

Now, Tickets also get created. These are the types of tickets you sell (and used to sell or issue)--associated with the opportunities of their actual issuance to each attendee.

Imported Data Ignored Before Cutoff Date

In the Elevent Salesforce app, you can set a cutoff data where all sales before that cutoff date will be ignored.

Imported customers and auto-assigned items, however, have no purchase date--so they weren't being ignored if they were imported before the cutoff date. We're talking about data imported into Elevent.

Now, imported data before the cutoff date will also be ignored if it happens before the cutoff date you specify.

The default address from Elevent will now map to Other Address

While you could already change this using the Field Mapping tool in our Salesforce app, we changed the default mapping of addresses from Elevent into Other Address. The carefully collected addresses of contacts in Salesforce are often more valued than the billing address from purchases; by changing this default, we tread more carefully around addresses that might already exist.

Concessions & Merch Added to Order Rollup

The calculated values for tangible items wasn't being populated

Changed all API URLs to the new elevent.app

Has no noticeable effect other than future-proofing.

Bug Fixes:

  • On-demand processing will now also use the configured batch size.
  • Removed a bug stopping changes to field mapping in the field mapping tool
  • Partially saved Elevent Update ignored on retry.
  • Address line 2 was getting dropped during processing.
  • Fix field mapping concession references.
  • Fix person account User ID mapping causing query row limit.