Elevent for Salesforce v2.8 is out. It brings in all of a customer's addresses from Elevent, not just one, and gives you real control over where Elevent data lands in Salesforce: when you send an Elevent field to a field of your choosing, it now replaces the default instead of writing to both. The Field Mappings screen has been rebuilt to make all of that easier to see.
If you're upgrading and you've set up custom field mappings, read Before you upgrade below first.
Multiple Customer Addresses
Elevent customers can have a Billing address, a Mailing address and a Seasonal address. Until now, only one of them made it into Salesforce.
Now all three sync:
- Billing goes where it always has: the contact's (or person account's) Other Address, unless you've mapped it elsewhere.
- Mailing and Seasonal go to new Elevent Mailing and Elevent Seasonal fields. Your standard Salesforce Mailing Address is left alone, because the addresses your team has carefully collected in Salesforce are often the ones you trust most.
Add the new fields to your contact or person account page layouts to see them.

When a customer removes an address in Elevent, its fields are cleared in Salesforce. Existing customers' Mailing and Seasonal addresses fill in the next time that customer changes in Elevent; reprocessing older Elevent Updates won't fill them in.
Custom Field Mappings Now Replace the Default
The Field Mapping tool lets you send an Elevent field to a Salesforce field of your choosing. Before v2.8, Elevent kept updating the default field too, so you couldn't really stop Elevent from writing to it.
Now a custom mapping replaces the default. The default field keeps whatever value it already has, but Elevent stops updating it.
A few fields can't be remapped, because the app relies on them to match customers, create records and calculate totals: a contact's Elevent ID, Email, Last Name and Last Updated in Elevent, for example. These show a lock icon.

A Redesigned Field Mappings Screen
In Salesforce, switch to the Elevent app and open Field Mappings.

Each Elevent field now has one row with a single picker, a note of the default it replaces, search, and filters:
- Remapped: fields you've sent somewhere else. The default shown under each one is no longer updated.
- Needs attention: mappings the app can't apply, such as two Elevent fields sent to the same Salesforce field, or a field that's been deleted. Until you fix one, that Elevent value isn't saved anywhere, so fix these first. When a custom mapping collides with an active default, the default mapping wins. These problems are also recorded in Error Logs.
- Fixed: fields that can't be remapped.

Every change is checked before it's saved, and a change that would cause a problem is blocked with an explanation.
Before You Upgrade
If you use custom field mappings:
- In Elevent Settings, turn off Enable Processing of Imported Data. Leave imports on so new data waits in line.
- Upgrade.
- Open Field Mappings and check Remapped and Needs attention on each object mapping. Update any flows, validation rules, reports or integrations that read a default field that's no longer updated.
- Turn processing back on.
Upgrades can't be undone, so try it in a sandbox first if you have one. Full steps are in the Admin Guide under Updating the App.
Also in This Release
v2.8 includes the v2.7 changes:
- Payment details on Elevent Orders and their opportunities: payment method, last 4 digits and card expiration date. Full card numbers are never stored.
- SKU on merchandise products.
Bug Fixes:
- Number and Checkbox fields can now be chosen as custom mapping destinations.
- Choosing a different record type in the Field Mapping tool now saves, and custom objects now show their record types.
















button and tweak it to your liking.
and choose the merch you want to work with.
to save it.
to print a label or (




then 
