Static Resource for Upgrade Managed Packages

Important When you upload data through Static Resource, upload data for each release in sequential order. Each upload builds upon the previous version for compatibility and ensures the managed package features function properly. Don’t skip a data upload for one release and directly upload data for a later release.

.csv files contain data that need to be entered in the corresponding objects of the Salesforce Organization to run and allow usage without the need to create large amounts of setup data.

.csv files contain data such as:

• Templates for multiple application objects
• Mobility picklist information and translations
• Basic system configurations
• Synchronization setup
• Mobile app themes

The data in .csv files can change after every release, and the upgraded managed packages store this data in the objects and the packages can even adapt this data based on the requirement. It's important to not just import the data as provided with the new release, but it's mandatory to check whether the updates still fit your requirements without overriding important custom modifications.

For this purpose, we've provided these files in multiple versions:

• Object_XYZ.csv: This is the plain installation file, which always contains the latest information of all records. Customers who are starting from scratch can use these files.
• Object_XYZ - NEW 236.csv: This file contains only new records and if you have an upgraded version, these files don't prevent you to upload these records. Some changes, such as new sync rules, are important; ensure that you make the decision carefully. We recommend that you install all new records.
  

  Note For completely new .csv Files or objects, no separate new file is provided because it would have been a 1:1 copy of the file. Download files from RetailRepositoryData in Static Resources, and then upload the files to Salesforce by using dataloader.io. Use all files in the List of Static Resource Files to Upload topic that don't have a special comment on the upgrade case.

• Object_XYZ - MODIFIED 236.csv - This file contains only modified records for the object that's provided in an earlier release, and is now updated with certain values. If these updates fit your requirements, revisit the updates at a later point of time (for example, if you need a change in your basic configuration or if you want to know whether the existing settings are sufficient). Some changes, such as new sync rules, are important; ensure that you make the decision carefully. We recommend that you install all new records.

Important Most template data is provided only for the 0001 Sales Organization;to use different Sales Organizations, take further steps as necessary. If you adapt records that are provided for the 0001 Sales Organization as a .csv file, consider the previously steps mentioned for an upgrade process.

For example, if you adapt the Order_Template_0001 record, then two cases can occur:

• If there's no change in the Order_Template_0001 record in a subsequent release and considering an upgrade case, observe only the .csv files for the NEW and MODIFIED records, and your adaptation remains (the record isn't included because its values didn’t change from the Managed Package perspective).
• If changes are applicable for the Order_Template_0001 record in a subsequent release that can revert the values that you adapted, find the records in the modified .csv file and make a decision whether to take over changes in the release. Before uploading the files, perform the required modifications.

• Record Type Mapping
  After you upload a file by using dataloader.io, use this table to identify the fields that aren't mapped and then map the fields accordingly.
• Unmapped Fields
  When you upload a static resource file by using dataloader.io, don't map these fields.
• Additional Steps to Upgrade Managed Packages to Spring ’26
  To upload demo data for Spring ’26, perform these steps.
• Static Resources Upload for Earlier Releases
  Before you upload static resources for the current release, we recommend to upload or make sure that the static resources for the previous release have been uploaded sequentially.