Updating the Azavista managed package in Salesforce ensures that your organization benefits from the latest improvements, bug fixes, and integration enhancements provided by Azavista.

Package upgrades preserve existing configurations and data; however, they should always be performed in a controlled and validated manner.

Before You Begin (Recommended Preparation)

Before initiating the upgrade process:

Review the release notes provided by Azavista.
Perform the upgrade in a Sandbox environment first.
Verify any custom fields, Flows, validation rules, Apex triggers, or automations referencing Azavista package components.
Inform stakeholders if a short maintenance window is required.

Proper preparation minimizes disruption and prevents conflicts during deployment.

Step-by-Step: Updating the Managed Package

1. Obtain the Latest Package Link

Request the updated installation link from Azavista or use the new installation URL provided in the release communication.

2. Log in to Salesforce

Sandbox (recommended first)
Production (after successful validation)

3. Run the Package Installation Link Again

Open the updated package installation URL.

Since the package is already installed, Salesforce will detect the existing version and display:

Upgrade (instead of Install)

Click Upgrade to proceed.

4. Select Installation Settings

During the upgrade:

Choose Install for All Users (recommended for consistency).
Review component access permissions.
Confirm the acknowledgment checkbox if prompted (Non-AppExchange application).

Click Upgrade to continue.

5. Wait for Upgrade Completion

The upgrade duration depends on:

Org size
Data volume
Existing automations

Salesforce will send a confirmation email once the upgrade is complete.

Post-Upgrade Verification (Critical Step)

After the upgrade completes, validation is required to ensure continued integration stability.

1. Verify the Installed Version

Navigate to:

Setup → Installed Packages

Confirm that the updated package version number is listed.

2. Validate Azavista Admin Configuration

Open:

App Launcher → Azavista Admin

Confirm that:

The Endpoint URL is still correct.
The Webhook value remains unchanged.
Sync Status settings remain intact.

For detailed package configuration steps, refer to:
https://support.azavista.com/hc/en-us/articles/25706886018332-How-do-I-Configure-Salesforce-Package-Configuration-Required-Step

3. Test Synchronization

Perform controlled validation testing:

Create or update a test Contact in Salesforce.
Confirm successful synchronization to Azavista.
Review:
- Logs
- Inspect view
- Error handling

For complete integration validation steps, see:
https://support.azavista.com/hc/en-us/articles/24317600040348-How-do-I-Configure-External-CRM-Salesforce-Integration

If organization field mappings require review after upgrade, see:
https://support.azavista.com/hc/en-us/articles/25612618171420-How-do-I-Configure-and-Manage-Organization-Field-Mapping-s-for-Salesforce-Integration

4. Validate Customizations

Carefully review:

Flows referencing “Sync to Azavista” fields
Custom validation rules
Apex triggers (if applicable)
Field mappings within the External CRM integration

Ensure no automation blocks record updates or API calls.

If the Upgrade Fails

Common causes include:

Missing permissions
Metadata conflicts
Attempted modification of managed package components
Conflicting validation rules

Resolution Steps

Review the installation error log in detail.
Temporarily disable blocking validation rules or Flows (if safe).
Retry the upgrade.
Contact Azavista Support if the issue persists.

Important Notes

Managed package components cannot be edited directly.
Upgrades do not delete existing data.
Custom fields created outside the package remain unaffected.
Always upgrade Sandbox before Production.

Recommended Upgrade Flow

Upgrade Sandbox
Validate integration and synchronization
Perform regression testing
Schedule Production upgrade
Re-test after Production deployment

Related to