EleventWhat's new
← All updates
New FeatureFixElevent for Salesforce

Elevent for Salesforce v2.5

Elevent for Salesforce v2.5 is out. The headline feature is a much-needed feature that adds some additional settings you can set to have the Elevent app self-manage deletion and cleanup of older files. This is a huge piece towards making sure the Elevent for Salesforce app doesn't use more Salesforce storage space than it needs to.

Elevent Update Auto-Purging

When Elevent for Salesforce syncs data in from Elevent, it uses a 2-step process to make sure your data stays protected and up-to-date.

  1. First, all the new data--customers (contacts), items purchased (opportunities), orders, etc. is imported into an object called Elevent Updates. This in in-progress data--nothing you'll see yet in the data you use.
  2. Next, those Elevent Updates are processed. This is where the Elevent for Salesforce app checks to see if contacts and other data already exist, checks to make sure the new data is indeed newer, etc.

The history of these Elevent Updates is really useful when troubleshooting anything that doesn't look as expected. They don't get deleted after processing for that reason.

As the weeks and months pile up, those Elevent Updates can start to take up a lot of room in your very constrained Salesforce org. Auto-purging to the rescue.

In Salesforce, switch to the Elevent app.

image.png

In the Elevent Settings panel, you'll see the new Log Cleanup section.

image.png

Enable it (Highly recommended). The default retention period is 30 days, but you can change it. Press the image.png button and tweak it to your liking.

Note this only auto-purges those in-progress records like Elevent Updates. This will not touch the customer and opportunity data you actually rely on. Also, it will only delete Elevent Updates that are Successful or Ignored--if something might have had an issue, those will remain until manually deleted.

Bug Fixes:

  • Fixed a bug causing overuse of imported data when updating the LastUpdatedDateTime stamp. This was the main bug causing storage use to grow over time.
  • Fixed a scheduled job status display bug: Job wouldn’t show as scheduled in the settings component even when it is.