Salesforce Core Package Upgrade Reinstallation Instructions

When upgrading to the 25.12 release of Cloud Connect for Salesforce, to ensure a clean installation and avoid duplicate components, we recommend performing a fresh installation of the Experlogix package family rather than an upgrade. While the upgrade process requires nearly the same steps as a reinstall, it can leave behind outdated components in the Salesforce environment, resulting in a less clean setup.

Reinstallation Workflow

To maintain a clean Cloud Connect environment and avoid component duplication when moving from legacy Experlogix Xplx versions, perform a full reinstallation rather than an upgrade. This approach removes residual legacy components left by upgrades and establishes a clean baseline without affecting business data or integrations.

Process Flow Overview

The following flow illustrates the end-to-end sequence for uninstalling legacy packages, installing Cloud Connect 25.12, restoring settings, and validating functionality.

1. Preparation

   1. Prepare a working note to track uninstall conflicts and metadata to restore later.

   2. Back up Experlogix Settings stored in Salesforce (e.g., CPQ/Cloud Connect mappings).

   3. Connected App configuration remains unchanged and does not require export.

2. Uninstall Existing Package

   1. Uninstall extension packages first (e.g., CPQ Actions, UI Buttons), then uninstall the main Experlogix package.

   2. Expect uninstall blocks when dependent metadata references packaged components.

3. Resolve Dependency Conflicts

   1. Document each conflict reported by Salesforce: (Flows, Buttons, Lightning pages, Process Builder/Flow, Apex references).

   2. Remove or temporarily disable the dependent metadata (deactivate flows, remove buttons, edit Lightning pages, remove references).

   3. Retry the uninstall and iterate until all Experlogix packages are removed.

4. Install New Package

   1. Install the latest core package.

   2. Install required extension packages, if applicable.

5. Restore Settings and Metadata

   1. Re-enter the Experlogix Settings backed up during preparation.

   2. Recreate or restore metadata removed during conflict resolution (Buttons, Flows, Lightning components/pages, etc.).

6. Sanity & Functional Validation

   1. Validate (Cloud Connect communication and CPQ configuration synchronization.

   2. Create a test Quote and run core user flows.

   3. Verify all restored components (buttons, flows, UI) function as expected.

Data & Integration Impact

• No Salesforce or CPQ data is modified or deleted during this procedure.

• Integration between Salesforce and CPQ remains intact (Cloud Connect and Connected App).

• Only Experlogix Settings within Salesforce require re-entry after the reinstall.

Upgrade Process Description

Considerations

The Experlogix (Xplx) packages do not store configuration data within the managed package itself.

If the setup references the CopyConfig flow or invocable Apex classes, verify that these references remain valid after reinstallation. Existing DevOps processes will not be affected, as all component names and namespaces remain unchanged.

Before reinstalling, export all Connection Settings. Secret values (such as authentication tokens or passwords) cannot be exported or imported and must be manually saved.

Before performing any manual updates, use Salesforce Workbench to retrieve all relevant Flows, Quick Actions, Page Layouts, and FlexiPages.

Copy Configuration flows are impacted by the reinstall and must be manually updated. However, the CopyConfig button created following Experlogix instructions is implemented as a link and does not require modification; it will continue to function as expected after the reinstall.

Permission Set Assignments must be recreated, and Permission Set Groups should be reviewed and backed up before reinstallation.

All Lightning Web Component (LWC) buttons must be deleted and recreated. Retrieval and deployment using metadata tools will continue to work, as component names remain unchanged. The following buttons are affected:

• PopUpCpqNewTab

• PopupCpq

• Recalculate

The following configurations are not affected by the reinstall and will remain intact:

• Whitelisted URLs and Remote Site Settings

• CPQ setup and CPQ server configuration

• Connection IDs and other Admin Center settings

• Process Designs

The migration must be performed by the System Administrator user.

Tools

Dataloader.io

Dataloader.io is part of the Salesforce ecosystem and has a link from the native setup application. It is an industry standard for small dataload operations.

Developer Workbench

Workbench is part of the Salesforce ecosystem and is often used by the Salesforce admins and developers to interact with Salesforce Metadata and APIs. It is an industry standard for quick metadata-related operations.

Text Editor

Notepad++ or another text editor is required to modify import files.

Preparations for Uninstallation

In this section, the main uninstallation preparations are made. These are applicable to any environment and are not dependent on any customer customizations.

Create a Working Folder

The process will include the creation and modification of multiple XML and CSV files. Create a working folder in a format <customerName>-core-migration-<EnvironmentName>. Use this folder for any exports and imports made during the migration process.

Experlogix Connection Settings backup

In this step, the Experlogix Connection Settings are backed up. Navigate to Experlogix App Connection Settings and export the settings.

Make sure that the Integration Client Secret & Integration Client Password are saved and ready.

Copy Configuration Flow Deactivation

In this step, we have to deactivate a packaged Screen Flow. Having active packaged flows will make uninstallation fail.

1. Navigate to Setup > Flows and locate the Copy Configuration Screen flow.

2. Select the drop-down to the right and select View Details and Versions.

   

3. Deactivate the active flow version.

   

Logging in to Dataloader.io

1. Navigate to Setup > My Domain and write down My Domain Name. This will be referred as OrgsMyDomain.

   

2. Navigate to Setup > Dataloader.io and Select Launch Dataloader.io.

   

3. Confirm the redirect.

4. Select Login with Salesforce.

   

5. Select the Environment type(production/sandbox) and select Login.

If logging in doesn't work, try checking if you have a custom Salesforce Domain. Use OrgsMyDomain acquired before, the Domain must be in the format <OrgsMyDomain>.my.salesforce.com.

Backup Permission Set Ids for Future Reference

1. Navigate to Dataloader.io.

2. Select New Task & Export.

   

3. Select the PermissionSet as the object and select Next.

   

4. Expand the SOQL Query and paste in the following query:

   SELECT Id, Name FROM PermissionSet WHERE Name IN ('Experlogix_Logger_Admin', 'Experlogix_Settings_Admin', 'Experlogix_Settings_User', 'Experlogix_CPQ_User', 'Experlogix_Buttons_Classic')

5. Select Close and then Next.

   

6. Select Save & Run.

7. Wait for the job to finish (1-2min) and refresh the page.

8. Select Successes to download the export results.

   

9. Name this file OldPermissionSetIds.csv.

Permission Set Groups Settings Backup

In this step we use Dataloader.io to back up customer customizations related to Experlogix Permission Sets. After the package is reinstalled, these will be imported back.

1. Navigate to Dataloader.io.

2. Select New Task and then Export.

   

3. Search for and select the PermissionSetGroupComponent object.

   

4. Select Next.

5. Expand the SOQL Query and paste in the following Query:

   SELECT Id, PermissionSetGroupId, PermissionSetGroup.DeveloperName, PermissionSetId, PermissionSet.Name FROM PermissionSetGroupComponent WHERE PermissionSet.Name IN ( 'Experlogix_Buttons_Classic', 'Experlogix_Settings_User', 'Experlogix_Settings_Admin', 'Experlogix_Logger_Admin', 'Experlogix_CPQ_User' )

6. Close the warning pop-up and select Next.

7. Select Save & Run.

   

8. Allow the export to run 1-2 minutes and refresh the page to download the resulting *.csv file. After clicking the Successes link, the *.csv download begins.

   

9. Name this file PermissionSetGroupComponentExport.csv.

Deleting Experlogix Permission Sets from Custom Permission Set Groups

In this step we use the Dataloader.io PermissionSetGroups backup CSV file to delete references to Experlogix Permission Sets.

1. Navigate to Dataloader.io.

2. Select New Task and then Delete.

   

3. Search for and select the PermissionSetGroupComponent object.

   

4. Select Next.

5. Select Upload CSV.

   

6. Select the file saved in the previous section.

   

7. Map the first field as an ID field.

   

8. Select Next.

9. Select Save & Run.

Permission Set Assignment Backup

In this step, all users' assignments to Experlogix Permission Sets assignments are being backed up using Dataloader.io .

1. Navigate to Dataloader.io.

2. Select New Task & Export.

   

3. Search for and select the PermissionSetAssignment object.

   

4. Select Next.

5. Expand the SOQL Query and paste in the following query:

   SELECT Id, PermissionSetId, PermissionSet.Name, AssigneeId, IsActive, ExpirationDate FROM PermissionSetAssignment WHERE PermissionSet.Name IN ('Experlogix_Buttons_Classic', 'Experlogix_Settings_User', 'Experlogix_Settings_Admin', 'Experlogix_Logger_Admin', 'Experlogix_CPQ_User')

6. Close the warning pop-up and select Next.

7. Select Save & Run.

   

8. Allow the export to run 1-2 minutes and refresh the page to download the resulting *.csv file. After clicking the Successes link, the *.csv download begins.

   

9. Locate this file and rename it to PermissionSetAssignmentExport.csv.

Permission Set Assignment Removal

In this step, we use Dataloader.io PermissionSetAssignments backup .csv file to delete references to Experlogix Permission Sets.

1. Navigate to Dataloader.io.

2. Select New Task and then Delete.

   

3. Search for and select PermissionSetAssignment object.

   

4. Select Next.

5. Select Upload CSV.

   

6. Select the file acquired in the previous section.

   

7. Map the first field as an ID field.

   

8. Select Next.

9. Select Save & Run, then Run in the confirmation dialog.

   

Packages Uninstallations and Further Backups Strategy

After the main settings have been saved, it can be difficult to identify all customizations that exist in the subscriber’s Salesforce environment. The recommended approach is to attempt the package uninstall and review any errors that occur. These errors typically indicate customizations that prevent the uninstall process from completing. Each blocking customization should be backed up and then removed before proceeding.

CPQ buttons for Salesforce Classic UI uninstallation

This package setup depends on links to our components instead of a direct reference, so the only potential failure could happen if Experlogix Buttons Classic is still assigned to users. If this happens, ensure both the Permission Set Assignment removal and the Deleting Experlogix permission sets from custom Permission Set Groups are successfully completed. If the setup was made according to Experlogix guidelines, the buttons will be available after the upgrade without any additional setup.

1. Navigate to Setup > Installed Packages.

2. Select the Uninstall link next to Experlogix Cloud Connect - CPQ buttons for Salesforce Classic UI package.

   

3. Select the Do not save a copy of this package's data after uninstall.

   

4. After the dialog displays, select OK.

5. Select Yes, I want to uninstall this package and permanently delete all associated components.

6. Select Uninstall.

The uninstallation can be monitored in the Setup-Installed Packages.

CPQ Action Templates Uninstallation

Copy Configuration Flow Deactivation

Before uninstallation, flow templates that implement this feature should be verified. If there are new versions, we have to back up the last active version and restore it later.

1. Navigate to Setup > Flows.

   

2. Locate Copy To Current Quote Filtered List and Copy To Current Opportunity Filtered List.

   

3. In the far right, select the drop-down icon and select View Details and Versions.

4. If the active version is not 1, make a note, that a deployment of the copy flow templates backup will be required.

   

5. Deactivate the active version.

   

6. Repeat the process for Copy To Current Opportunity Filtered List.

7. If the active version is not 1, make a note, that a deployment of the copy flow templates backup will be required.

8. Deactivate the active version.

Customer modified Copy Configuration Flow Template metadata backup

In this section, the Workbench is used to retrieve Flow metadata.

1. Navigate to https://workbench.developerforce.com/

2. Select the Environment type.

3. Select Login with Salesforce.

   

4. Select Migration > Retrieve.

   

5. Use attached file or create the retrieve-copy-flows-package.xml and use it in the workbench.

   <?xml version="1.0" encoding="UTF-8"?>
   <Package xmlns="http://soap.sforce.com/2006/04/metadata">
   <types>
   <members>Xplx__Copy_To_Current_Opportunity_Filtered_List</members>
   <members>Xplx__Copy_To_Current_Quote_Filtered_List</members>
   <name>Flow</name>
   </types>
   <types>
   <members>Xplx__Copy_To_Current_Opportunity_Filtered_List</members>
   <members>Xplx__Copy_To_Current_Quote_Filtered_List</members>
   <name>FlowDefinition</name>
   </types>
   <version>62.0</version>
   </Package>
   

6. Select Next.

7. Select Retrieve.

   

8. The retrieve request will run for some time, after which the results have to be downloaded using the Download ZIP File button.

   

9. Name the file CopyConfigurationFlowTemplateBackup.zip.

Package uninstallation

In this step the package uninstallation will be initiated.

1. Navigate to Setup > Installed Packages.

2. Select Uninstall link next to Experlogix Cloud Connect - CPQ Action Templates package.

   

3. Select Do not save a copy of this package's data after uninstall. After dialog displays, select OK.

   

4. Select Yes, I want to uninstall this package and permanently delete all associated components.

5. Select Uninstall.

The uninstallation can be monitored in the Setup-Installed Packages.

Experlogix Cloud Connect for Salesforce

During the initial uninstall attempt, the process will cancel just before starting. This is expected behavior and helps identify any customizations or dependencies that must be addressed before a successful uninstall. The following types of errors may occur:

• Lightning Web Component (LWC) references: These components are typically used as Quick Actions (buttons) to run CPQ, Copy, or Recalculate features. Each referenced component should be backed up before removal.

• CopyConfig flow references: This may occur if the customer has cloned one of the Copy Configuration templates, resulting in a custom flow that references Experlogix components. These custom flows should be backed up and restored after reinstallation.

• Active CopyConfig flows: This error can occur if a prior step was missed and the CopyConfig flow remains active. Ensure all relevant flows are deactivated before proceeding.

• Permission set-related errors: If permission set-related errors appear, confirm that all permission set assignments have been removed and that the corresponding Permission Sets have been removed from any Permission Set Groups. See Permission Set Assignment removal and Deleting Experlogix permission sets from custom Permission Set Groups for more information.

Initial Uninstallation Run

In this step, an uninstallation process of the main package is initiated for the first time. Multiple errors are expected.

1. Navigate to Setup > Installed Packages.

2. Select Uninstall link next to Experlogix Cloud Connect for Salesforce package.

   

3. Select Do not save a copy of this package's data after uninstall. After dialog displays, select OK.

   

4. Check Yes, I want to uninstall this package and permanently delete all associated components.

5. Select Uninstall.

6. Select Uninstall .

Below is the example of how initial run might go. These references should be backed up and removed.

Dealing with QuickActions (Lightning Web Component references)

Backup of Quick Actions

Quick action references are highlighted by the following line. The word "action" tells that this is a quick action. Lightning Web Component Bundle means that the reference is made to LWC.

Creation of the cpq-quick-actions-backup-package.xml File

The package file for data retrieval has to be created first.

1. Create a cpq-quick-actions-backup-package.xml and paste the following data into it.

   <?xml version="1.0" encoding="UTF-8"?>
   <Package xmlns="http://soap.sforce.com/2006/04/metadata">
   <types>
   <members>Quote.CPQ</members>
   <members>Quote.Recalculate</members>
   <name>QuickAction</name>
   </types>
   <version>62.0</version>
   </Package>
   

<types>
<name>QuickAction</name>
</types>

While on Uninstallation failed page from the Initial Uninstallation Run step, for every Lightning Web Component dependent action repeat the following:

2. Right click on the action name and Open in a new window.

   

3. When the Quick action page opens, note the Name and Object Name field values.

   

4. Add a member item to cpq-quick-actions-backup-package.xml file in the format ObjectName.Name.

5. Repeat until all QuickActions are mentioned in the *cpq-quick-actions-backup-package.xml file.

QuickAction Backup Using Workbench

1. Navigate to https://workbench.developerforce.com/

2. Select the Environment type.

3. Select Login with Salesforce.

   

4. Select Migration > Retrieve.

   

5. Select the cpq-quick-actions-backup-package.xml file and select Next.

6. Select Retrieve

   

7. Wait for the results and download the zip file.

   

8. Locate the file and rename it to QuickActionsBackup.zip.

Backup of the Layouts and FlexiPages

Creation of the cpq-layouts-and-flexipages-backup-package.xml File

Once all Quick Actions have been backed up, they can be safely removed. However, before doing so, any Page Layouts and FlexiPages that reference these Quick Actions must also be backed up and cleaned. This step was not performed earlier because identifying which layouts reference the Quick Actions requires first attempting to delete the Quick Actions themselves. This process will reveal the dependencies that need to be updated.

1. Create a cpq-layouts-and-flexipages-backup-package.xml and paste the following data into it.

   <?xml version="1.0" encoding="UTF-8"?>
   <Package xmlns="http://soap.sforce.com/2006/04/metadata">
   <types>
   <members>Quote-Quote Layout</members>
   <members>Custom__c-Custom Layout</members>
   <name>Layout</name>
   </types>
   <types>
   <members>Quote_Record_Page</members>
   <name>FlexiPage</name>
   </types>
   <version>62.0</version>
   </Package>
   

<types>
<name>FlexiPage</name>
</types>

2. Return to Uninstallation failure screen from Initial Uninstallation Run step or run the uninstall again.

3. For every Lightning Web Component dependent action repeat the following:

4. Right click on the action name and select Open in a new window.

5. Select Delete and OK.

6. If the deletion was sucessful, proceed to the next QuickAction. In most cases an error is thrown showing where this QuickAction is referenced.

   

Backup file preparation for Lightning Pages(Flexipages)

1. For record page type of references(Flexipage) open link in a new window to get to the Lightning Page(Flexipage) screen

   

2. Note the Name field's value and add a new into the cpq-layouts-and-flexipages-backup-package.xml to part of the file.

Backup File Preparation for Page Layouts

For layout items add the Layout Name as a new member into Layout part of the cpq-layouts-and-flexipages-backup-package.xml file. The Format is <ObjectName>-<Layout name>

Layouts and Flexipage Backup Using the Workbench

1. After completing the file, navigate to https://workbench.developerforce.com/

2. Select the Environment type.

3. Select Login with Salesforce.

   

4. Select Migration > Retrieve.

   

5. Select the cpq-quick-actions-backup-package.xml file and select Next.

6. Select Retrieve.

   

7. Wait for the results and download the zip file.

   

8. Locate the file and rename it to LayoutsandFlexipagesBackup.zip.

Cleanup of the Layouts and FlexiPage

Cleanup of the Layouts

Once all Page Layouts have been backed up, the Quick Actions can be removed. For each layout listed in the cpq-layouts-and-flexipages-backup-package.xml file, complete the following steps:

1. Navigate to Setup > Object Manager and quick find for desired object.

   

2. Navigate to Page Layouts and select the required Layout.

   

3. Remove the required quick actions from the layout by dragging them back to the pane.

   

4. Save the Layout.

Cleanup of the Flexipages

Using cpq-layouts-and-flexipages-backup-package.xml for reference.

1. Navigate to Setup >Object Manager and quick find for desired object.

   

2. Navigate to Buttons, Links and Actions and select the desired action.

   

3. Select Delete and OK. We expect the error screen again.

4. Open the Flexipage by following its link.

   

5. Select Edit on the lightning page screen.

   

6. Select the Header Component to open Dynamic Actions panel.

   

7. Scroll down and delete the desired Quick Action.

Removal of the Quick Actions

Use QuickActionsBackup.zip for reference and repeat for every QuickAction.

1. Navigate to Setup > Object Manager and quick find for desired object.

   

2. Navigate to Buttons, Links and Actions and select the desired action.

   

3. Select Delete and OK.

Dealing with CopyConfigurationScreen Flow References

In this step, custom flows referring CopyConfigurationScreen are backed up and removed.

Verify if there are References to CopyConfiguration Flow

1. Get Back to Uninstallation failure screen fromInitial Uninstallation Run or run the uninstall again.

2. CopyConfigurationScreen references are marked with red. If there are not references, proceed to Final uninstallation run.

   

Creation and Population of the ustom-copy-flows-package.xml File

1. Create the custom-copy-flows-package.xml file with the following contents

   <?xml version="1.0" encoding="UTF-8"?>
   <Package xmlns="http://soap.sforce.com/2006/04/metadata">
   <types>
   <members>FLOW_NAME</members>
   <name>Flow</name>
   </types>
   <types>
   <members>FLOW_NAME</members>
   <name>FlowDefinition</name>
   </types>
   <version>62.0</version>
   </Package>
   

For each CopyConfigurationScreen reference add a <member> into the custom-copy-flows-package.xml file, so according to the example. The Api Name of the flow is provided in the uninstallation failed screen and can be copied as is.

<members>Custom_Copy_To_Quote_Flow</members>

If there are multiple version of the flow and old version are required to be backed up - add members with a version number followed by -. Note that the metadata file for last version will not have -# prefixed and will just have the name of the flow(Custom_Copy_To_Quote_Flow). FlowDefinition file will control which version is active.

<members>Custom_Copy_To_Quote_Flow-1</members>
<members>Custom_Copy_To_Quote_Flow-2</members>
<members>Custom_Copy_To_Quote_Flow-3</members>

Custom Copy Configuration Flows Backup using Workbench

1. After completing the file, navigate to https://workbench.developerforce.com/

2. Select the Environment type.

3. Select Login with Salesforce.

   

4. Select Migration > Retrieve.

   

5. Use the custom-copy-flows-package.xml file and select Next.

6. Select Retrieve.

   

7. Wait for the results and download the zip file.

8. Locate the file and rename it to CustomCopyFlowsBackup.zip.

CopyConfigScreen Reference Removal from Custom Copy Configuration Flows

Should be done after Custom Copy Configuration Flows Backup using Workbench step. Iterate through custom-copy-flows-package.xml file to process all required flows.

1. Navigate to Setup > Flows.

2. On the far right of the required flow click the dropdown icon and select View Details and Versions.

   

3. Remove all inactive version of the flow using the Del link.

4. Select OK in the dialog.

5. Open the active version using Open link

   

6. Locate a Subflow element that references Copy Configuration Screen.

   

7. Select the ellipsis on the element and then Delete the element.

8. Select Save As New Version.

9. Select Save.

   

10. Select Activate.

    

11. Go back to Setup > Flows.

12. Locate the same flow and select View Details and Versions.

13. Remove one last inactive version(the version that was overwritten by the change in this step.

14. Select OK in the dialog. Now the active version is not referring to the CopyConfigScreen flow.

Final Uninstallation Run

In this step, an uninstallation process of the main package in initiated after backing up and removing all references.

1. Navigate to Setup > Installed Packages.

   

2. Select Uninstall link next to Experlogix Cloud Connect for Salesforce package.

3. Select Do not save a copy of this package's data after uninstall.

   

4. After dialog displays, select OK.

5. Check Yes, I want to uninstall this package and permanently delete all associated components.

6. Select Uninstall.

7. Select Uninstall. The uninstallation can be monitored in the Setup-Installed Packages.

   

Installation of the new packages

Core package installation

Use the following link to install the Experlogix Cloud Connect For Salesforce package.

CPQ Extension package installation

Use the following link to install the Experlogix Cloud Connect - CPQ Extension package.

CPQ Buttons For Salesforce Classic UI package installation

Not every customer is using this extension. Install only if it was uninstalled during previous phases. Use the following link to install the Experlogix Cloud Connect - CPQ Buttons For Salesforce Classic UI package.

CPQ Action Templates package installation

Not every customer is using this extension. Install only if it was uninstalled during previous phases. Use the following link to install the Experlogix Cloud Connect - CPQ Action Templates package.

Restoration of Removed Dependencies

Now, when the packages have been reinstalled all removed settings have to be brought back.

Acquire Renewed Experlogix Permission Set Ids

1. Navigate to Dataloader.io.

2. Select New Task & Export.

   

3. Select PermissionSet as the object.

   

4. Select Next.

5. Expand SOQL Query and paste in the following query:

   SELECT Id, Name FROM PermissionSet 
   WHERE Name IN ('Experlogix_Logger_Admin', 'Experlogix_Settings_Admin', 'Experlogix_Settings_User', 'Experlogix_CPQ_User', 'Experlogix_Buttons_Classic')
   

6. Select Close in the dialog.

   

7. Select Next.

8. Select Save & Run.

   

9. Wait for the job to finish (1-2min) and refresh the screen.

10. Select Successes to download export results.

    

11. Name this file NewPermissionSetIds.csv.

Apply New Permission Set IDs to PermissionSetAssignmentExport.csv

After the packages have been uninstalled, all associated components are deleted. When the packages are reinstalled, these components are regenerated with new IDs. As a result, the backup files created earlier still reference the old, deleted IDs. In this step, a combination of data exports is used to update the contents of the PermissionSetAssignmentExport.csv backup file so that it references the new component IDs before being reimported into Salesforce.

1. Create a copy of PermissionSetAssignmentExport.csv and name it PermissionSetAssignmentImport.csv.

2. For each Id in OldPermissionSetIds.csv file, using a PermissionSet.Name field value, match a corresponding Id from NewPermissionSetIds.csv file and replace the old ID with the new ID in PermissionSetAssignmentImport.csv. Every record's PermissionSetId should get an updated value.

   

Apply new Permission Set Ids to PermissionSetGroupComponentExport.csv

Similar to the previous step, the old Permission Set IDs must be replaced with the new IDs from the latest export. Update the PermissionSetGroupComponentExport.csv backup file accordingly before reimporting it into Salesforce.

1. Create a copy of PermissionSetGroupComponentExport.csv and name it PermissionSetGroupComponentImport.csv.

2. For each Id in OldPermissionSetIds.csv file, using a PermissionSet.Name field value, match a corresponding Id from NewPermissionSetIds.csv file and replace the old Id with the New Id in PermissionSetGroupComponentImport.csv. Every record's PermissionSetId should get an updated value.

   

Restoration of Permission Set Assignments

1. Navigate to Dataloader.io.

2. Select New Task & Import.

   

3. Select PermissionSetAssignment.

   

4. Select Next.

5. Select the PermissionSetAssignmentImport.csv file created in the Apply New Permission Set IDs to PermissionSetAssignmentExport.csv.

   

6. Select Next.

7. Keep the default mapping and select Next.

   

8. Select Save & Run.

   

9. Select Run.

10. Verify that the result is successful.

    

Restoration of Permission Set Group Assignments

1. Navigate to Dataloader.io.

2. Select New Task & Import.

   

3. Select PermissionSetGroupComponent.

   

4. Select Next.

5. Select PermissionSetGroupComponentImport.csv file created in the Apply new Permission Set Ids to PermissionSetGroupComponentExport.csv step.

6. Select Next.

7. Keep the default mapping and select Next.

   

8. Select Save & Run.

   

9. Select Run.

10. Verify that the result is successful.

    

Restoration of Cloud Connect Settings

Once the packages are installed, the Experlogix application along with the Setup page should be available again.

1. Navigate to the Experlogix app → Connection Settings.

2. Import the settings backup that was created during the Experlogix Connection Settings backup step.

   

Restoration of Flows

Restoration of Copy Configuration customized template flows.

Work with filenames and package.xml

1. Unpack CopyConfigurationFlowTemplateBackup.zip and rename the folder to CopyConfigurationFlowTemplateImport.

2. Remove the Xplx__ prefix from all filenames.

3. Edit the package.xml file to remove all Xplx__ references.

4. Pack the folder back to zip so the result file is named CopyConfigurationFlowTemplateImport.zip.

   

Deployment of CopyConfigurationFlowTemplateImport.zip using Workbench

1. Navigate to https://workbench.developerforce.com/.

2. Select the Environment type and select Login with Salesforce.

   

3. Select Migration > Deploy.

   

4. Select CopyConfigurationFlowTemplateImport.zip file.

   

5. Select Next.

6. Select Deploy.

   

Restoration Of QuickActions

1. Navigate to https://workbench.developerforce.com/.

2. Select the Environment type and select Login with Salesforce.

   

3. SelectMigration > Deploy.

   

4. Select QuickActionsBackup..zip file.

5. Select Next.

6. Select Deploy.

Restoration of Layouts and Flexipages

1. Navigate to https://workbench.developerforce.com/.

2. Selectthe Environment type and select Login with Salesforce.

   

3. SelectMigration > Deploy.

   

4. Select QuickActionsBackup..zip file.

5. Select Next.

6. Select Deploy.

Restoration of Customer flows referring CopyConfigurationScreen

1. Navigate to https://workbench.developerforce.com/.

2. Selectthe Environment type and select Login with Salesforce.

   

3. SelectMigration > Deploy.

   

4. SelectQuickActionsBackup..zip file.

5. Select Next.

6. Select Deploy.