Skip to content
  • There are no suggestions because the search field is empty.

Salesforce Upgrade Guide

This guide walks Salesforce Admins through upgrading the Consensus managed package to the latest version (currently 11.13). Steps vary slightly depending on which version you’re currently running, so check the sections below to find your path.

How to Upgrade Your Consensus Salesforce Package

Not sure what version you’re on? In Salesforce, go to Setup → Installed Packages → Consensus.

Before You Begin

1.) You’ll need Salesforce System Administrator access to complete this upgrade.

2.) After the upgrade completes, you’ll need to manually trigger a full data resync by clicking Run Data Update on the Configuration tab in Salesforce. This doesn’t happen automatically and it may take some time depending on your data volume. The recent-data scheduled jobs won’t start running on their configured interval until one full sync has completed successfully so don’t skip this step.

Review the Special Cases below first. If none apply to you, skip to Standard Upgrade Steps.

Special Case: Running Version 6.x or Earlier

If you’re on version 6.x or below, you cannot upgrade directly. These versions require a full package uninstall and fresh reinstall, along with a data migration plan.

Action: Please contact your Consensus CSM to scope this as a migration project before proceeding. Do not attempt a standard upgrade.

Special Case: Running 11.5.3 or an Earlier 11.5.x/Pre-11.6 Build

Orgs on these builds may hit an AuraDefinitionBundle error during upgrade. This is caused by the legacy pre-OAuth “Invites” Lightning component, which has been retired.

Action: Before upgrading, find and remove the old InvitesComponent from your page layouts:

  1. In Salesforce, go to Setup → Object Manager.
  2. Check the page layouts for your Account, Opportunity, Contact, and Lead objects.
  3. Locate the legacy InvitesComponent on each layout where it appears, and remove it.
  4. Save your changes, then proceed with the standard upgrade steps below.

Orgs already on 11.6 or later are not affected by this and can upgrade normally.

Special Case: Running 11.5.x or 11.6.x

These versions cannot upgrade directly to 11.8 or later. You’ll need to upgrade to 11.9 first, then run the upgrade again to reach the latest version. Reach out to us for additional help.

Standard Upgrade Steps

Applies to versions 7.x through 11.12.x that don’t fall into a special case above.

Step 1: Install the Update via Salesforce AppExchange

  1. Navigate to the Consensus Professional app listing on the Salesforce AppExchange.
  2. Click Install in Production.
  3. Review and accept the terms and conditions, then confirm the install.

Installation may take some time to complete, especially if your org is running other scheduled jobs concurrently.

Step 2: Reconnect via OAuth 2.0 (if on 11.12.3 or below and connected with an API key and secret)

Consensus now uses OAuth 2.0 in both directions, so there’s no API key or secret to paste and no public Salesforce Site to maintain. There are two connections to check.

Salesforce to Consensus (the package’s connection):

  1. In Salesforce, open the Consensus app’s Configuration page and click Connect.
  2. Log in to Consensus and approve access. You’ll be returned to the Configuration page.

If this connection ever stops working (for example, a revoked token), click Reconnect. It first tries a token refresh and only re-registers the connection if that fails.

Consensus to Salesforce (CRM Sync follow this guide: CRM Sync connection):

  1. In the Consensus webapp, go to Integrations → Salesforce.
  2. Click Connect and enter your Salesforce CRM URL.
  3. Log in with your admin credentials and accept the requested permissions.
  4. Once connected, your status will show as Connected, and a new Configurations tab will appear.

Your existing CRM Sync and Auto-Matching settings will carry over automatically. You can now safely disable or delete your old public Salesforce Site, as it’s no longer used.

Full walkthrough: Connecting Consensus to Salesforce (OAuth 2.0)

Step 3: Update Permission Sets

Older versions relied on cloning a Consensus profile or manually assigning individual permission sets. This is no longer necessary. The package now installs three permission set groups:

  • Consensus Admin Group for admins
  • Consensus User Group for standard end users
  • Consensus Integration Group for a dedicated integration user
  1. Assign the Consensus Integration Group to your integration user (see the license note below).
  2. Assign the Consensus User Group to standard end users, and the Consensus Admin Group to admins, rather than cloning profiles.
  3. If you’re not using an integration user, the running user just needs the Consensus Admin Group.
  4. Confirm your users have access to the new Discovery Q&A object so they can see discovery answers on Demo Views.
  5. Saleo customers: the Consensus permission sets now include edit access to the two Saleo Account fields, so no extra permission set is needed.

Optional but recommended: If you’re using a dedicated integration user, you can save on license costs:

  • User License: Salesforce Integration
  • Profile: Minimum Access - API Only Integrations
  • Assign the Salesforce API Integration Permission Set License before assigning the Consensus Integration Group

For a full list of permissions see: Install and Configure the Consensus Salesforce Professional App (Lightning)

Step 4: Clean Up Page Layouts and Reports

If you’re coming from a version prior to 11.6, your layouts likely still reference old related lists or deprecated components.

  1. Remove any legacy DemoBoard or Invitation related lists from your Account, Opportunity, Contact, and Lead layouts.
  2. Remove any deprecated Consensus components.
  3. Add the current Consensus Layout Component to the relevant object layouts. This shows DemoBoard and View data, plus summary stat cards, in a single embedded view.
  4. If you used the Opportunities w/ DemoBoards Report or Closed Opportunities Report, rebuild them on the Consensus Opportunities custom report type, since both reports and their Demolytics dashboard tiles are removed in 11.13.
  5. Optional: add “Saleo Influenced” and “Saleo Agent Influenced” to Account layouts, list views or reports if you use Saleo.

Step 5: Confirm the Update

  1. Return to Setup → Installed Packages and confirm the version number now reflects the latest release.
  2. In the Consensus app’s Configuration page, click Test Connection (for the versions before 11.12), then Run Data Update to kick off a fresh sync.
  3. Return to Setup → Jobs and confirm our batch jobs passed successfully.
  4. Once a discovery demo has been viewed and answered, open the DemoBoard → Invitations → Views → Question Answers to confirm the Q&As are syncing.

What’s New in 11.13 That Affects Your Upgrade

  • Discovery Q&A object: Discovery questions and answers from Consensus demos now sync to a new Discovery Q&A custom object. Each record holds one question and answer and is linked to a Demo View. The scheduled Views sync loads them along with Views and Features.
  • Deprecated fields removed: Custom fields on standard objects that were deprecated in 11.7 are removed from layouts, record pages, report types and reports. Unused flows and classes are also removed. If you built your own reports or layouts on those fields, review them after upgrading.
  • Two reports removed: The Opportunities w/ DemoBoards Report and Closed Opportunities Report are removed, along with their tiles on the Consensus Sales Demolytics dashboard. They relied on the “Has DemoBoards” field, which hasn’t been populated in a long time. Use the custom report type Consensus Opportunities instead, which includes Opportunities, DemoBoards, Invitations and Views.
  • Open opportunities in CRM Sync: The Select Opportunity dropdown now lists all open opportunities, and the related account fills in automatically in both the web app and SNAP. Closed opportunities are excluded from the list and from auto-match.
  • Account merges: When accounts are merged in Salesforce, DemoBoards linked to the deleted (losing) account are reassigned to the surviving account. This happens on the next data sync, not instantly. Regular account deletes (not merges) don’t trigger this. If your org has the Account trigger disabled under Configuration → Advanced Options, merged DemoBoards won’t be reassigned.
  • Saleo customers: Saleo revenue attribution requires 11.13 or later. On older versions Saleo detects the package, but writes to the two new Account fields (Saleo Influenced and Saleo Agent Influenced) fail until you upgrade.

Saleo Customers: Connect Salesforce in Saleo

After the package is on 11.13 or later, start the Salesforce connection in Saleo, log in (ideally with the dedicated integration user) and approve the access request. Saleo writes only the two Account checkboxes and never creates or changes leads, contacts, opportunities or activities.

Already on Version 11.12.4 or Later?

You’re already on OAuth. A standard AppExchange update (Step 1) is all you need, plus the permission check for the new Discovery Q&A object in Step 3. No reconnection is required.

On 11.10 to 11.12.3?

Complete Step 1. If your integration still connects with a pasted API key and secret, reconnect once using Step 2, then check permissions in Step 3.

Need Help?

If you run into errors during the upgrade that aren’t covered here, contact Consensus Support with your current version number and a screenshot of the error.