During the development and testing cycle, you might need to periodically install and uninstall packages before you install the next beta. Read through the sections to understand how to install CRMi.
Before installing Salesforce
- Coordinate time with SFDC administrator and complete the SFDC installation or the configuration of the CRMi package. The complete configuration is required within SFDC and Acoustic Campaign.
- Obtain a security token from the Salesforce user account that you plan on using for integration. The security token is used during setup and while you change the Salesforce password).
- Obtain the SFDC Organization ID (The organization ID is entered when you begin the mapping exercise within Acoustic Campaign).
- Make sure that you know your SFDC login credentials, that you need to enter in Acoustic Campaign during setup and while you change the Salesforce password.
- Get the latest install version (2.2).
- Enter your username and password for the Salesforce organization in which you want to install the package.
Note: If you are installing into a salesforce Sandbox, you must replace the beginning of the URL with http://test.salesforce.com. When installing into multiple Salesforce environments, it's best to use private browsing or incognito sessions for separate Salesforce logins when installing packages to avoid cookie and cache conflicts in Salesforce.
Follow these steps to install the package
- Log in to Salesforce as an administrator by using the AppExchange URL provided by Campaign.
- Select Install for All Users and click Install or Upgrade.
- The installation process takes a few minutes and you are notified about the package installation. If the package did not install successfully, contact your integration specialist with the specific error.
- Go to Setup > App Setup > Create > Objects and verify that the following objects are in a deployed status.
- Email Link
Optional install procedure for Person Accounts feature
If you have the Person Accounts feature enabled. You must install the core package as outlined. You must also install and configure an additional package outlined here.
Salesforce Package API
Our developers have released a package compatible with the following
Our "Apex Classes" and "Visualforce Pages" in version 2.1 uses Salesforce API versions 52 and greater.
To view the current Salesforce APIs used by our package, in Salesforce:
Go to Setup
In the Quick Find box search for "Apex Classes", "Visualforce Pages" or "Login history"
Use the Namespace Prefix "silverpop" to identify Acoustic "Apex Classes" or "Visualforce Pages" Components and the API versions currently being used
- Use the Login History to identify the Acoustic Campaign Logins for the integration.
Note: The Login History API has been updated to Salesforce supported versions as of April 26, 2022. Although the Acoustic server Login History will show the updated API version regardless of the package version, the integration features require updating the package in Salesforce to version 2.2 to work as expected.
Review our Acoustic Campaign Salesforce CRMi Packages and Salesforce AppExchange articles for more details.
The Salesforce release date for Summer ’22 will depend on your instance of Salesforce, but the main release weekends are
- May 21, 2022
- June 4, 2022
- June 11, 2022
If you already know the instance where your production org is located, go to Salesforce Trust, click on your instance name, and click Maintenance. This will show you the date of the Salesforce Summer ’22 release for your org.
- These are SOAP Web Service logins from Acoustic’s servers:
- Username: User specified in the Credentials login setup
- Login Type: Partner product
- Application: Vtrenz/spengage1/ (the original backend code name for the proprietary Acoustic Salesforce integration)
- API Type: SOAP Partner
Install and upgrade options
When clicking the package link, Salesforce Admins are automatically directed to the Salesforce login page.
Note: If you are installing into a salesforce Sandbox, you must replace the beginning of the URL with http://test.salesforce.com.
When installing into multiple Salesforce environments, it's best to use private browsing or incognito sessions for separate Salesforce logins when installing packages to avoid cookie and cache conflicts in Salesforce.
For these options, right-click on the link.
- For Chrome - select Copy link address or Open link in incognito window:
- For Firefox - select Copy Link or Open Link in Private Window:
After logging in, Salesforce Admins are presented with options to:
- Install for Admins Only
- Install for All Users
- Install for Specific Profiles
We suggest installing it for All Users.
Review the permissions needed for our features included with the package. Most important to note, the features in the package are being performed by the users specified in the Credentials tab in Acoustic Campaign, not the Salesforce user who happens to also have an Acoustic Campaign user login.
The Acoustic user is performing API calls to Acoustic Campaign, on behalf of all Salesforce users accessing the features in the package.
If choosing Specific Profiles, review Salesforce’s notes and instructions while selecting Access for each Profile. The profile for the Salesforce user in the credentials tab in Acoustic Campaign, as well as other Salesforce users who need to use the features, need to be included for "Full Access".
If Admins Only or Specific Profiles is selected, review Salesforce’s suggestions if problems occur for users who were not given access to the package.
If you install a package for Admins Only but later want to grant permissions to other profiles, you must do so manually by either assigning the appropriate permissions to the profiles or by creating a permission set and assigning it to the appropriate users.
Once a package is installed, re-installing it, and selecting a different "Install for..." option doesn't change existing rights. So, if you install something for admins only, but later want to make it available to more profiles, you must manually add the appropriate permissions.
Find out more about Managed Package: giving All Users access after installing for Admins Only.
A Salesforce Admin may have to manually assign the Acoustic CRMi App directly to the Permission Set or Profile