Salesforce Docs Portal

Additional Steps to Upgrade Managed Packages to Winter ’26

To upload demo data for Winter ’26, perform these steps.

Required Editions

Available in: Lightning Experience

Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled

User Permissions Needed
To upload static resources: System Administrator

Upload Static Resource Files

Download files from RetailRepositoryData in Static Resources, and then upload the files to Salesforce by using the dataloader.io insert or upsert operation. The .csv files contain data that you must enter into the corresponding objects of the Salesforce Org to run and use the files without the need to create large amounts of setup data.

If the static resource file uploads data for objects such as Promotion Template, Search Strategy, or System Number, then Handle Validation Rules

Note
Note For more information about unmapped fields that require mapping, see Record Type Mapping. For fields that don’t require mapping, see Unmapped Fields.
  1. From Setup, in the Quick Find box, enter Static Resources and select it.
  2. Download and extract the RetailRepositoryData.zip static resource file.
  3. From Setup, in the Quick Find box, enter Dataloader.io and select it.
  4. Click Launch dataloader.io and login with your org credentials.
  5. In dataloader.io, upload the files from only the RetailRepositoryData/Upgrade/256 folder.
    The CSV file that you upload is sometimes dependent on another CSV file. To prevent any errors, we recommend that you upload files in the sequence they are listed in the table.
    Important
    Important Even if a file upload is marked as optional, the upload depends on the business decision to use specific feature changes within that file. If the business chooses to implement these features, uploading the file is required. Otherwise, it's optional.
File name Object API Name Operation Mandatory or Optional Related To Nature of Change
System_Setting_-_NEW_258.csv System_Setting__c Insert Mandatory Direct Store Delivery (DSD) - Tour Checks Custom system setting is added to allow updates to tour checks for tours that are complete or canceled.
Custom_Permission_User_Role_Mapping_-_NEW_258.csv Custom_Permission_User_Role_Mapping__c Insert Mandatory Route sales user Custom permission record is added to user role mapping for route sales user.
Mobile_App_Domain_-_NEW_258.csv Sync_Mobile_App_Domain__c Insert Optional Direct Store Delivery (DSD) - Tour Checks New records are added for usage and check type picklists values.
Mobile_App_Picklist_Mapping_-_NEW_258.csv Sync_Mobile_App_PL_Map__c Insert Optional Direct Store Delivery (DSD) - Tour Checks New records are added for picklist mappings of usage and check type fields.
Order_Template_-_MODIFIED_258.csv Order_Template__c Upsert Optional Route sales user Records are modified to add route sales user role in user roles for DSD related order templates.

Upload Direct Store Delivery Static Resource Files

To use the Direct Store Delivery (DSD) and Van Sales feature, download files from RetailDSDData in Static Resources, and then upload the files to Salesforce by using the dataloader.io insert or upsert operation.

Note
Note For more information about unmapped fields that require mapping, see Record Type Mapping. For fields that don’t require mapping, see Unmapped Fields.

Make sure to upload demo data and complete the sync configuration for Retail Execution.

  1. From Setup, in the Quick Find box, enter Static Resources and select it.
  2. Download and extract the RetailDSDData.zip static resource file.
  3. From Setup, in the Quick Find box, enter Dataloader.io and select it.
  4. Click Launch dataloader.io and login with your org credentials.
  5. In dataloader.io, upload the files from the RetailDSDData/Upgrade/256 folder.

The CSV file that you upload is sometimes dependent on another CSV file. To prevent any errors, we recommend that you upload files in the sequence they are listed in the table.

Important
Important Even if a file upload is marked as optional, the upload depends on the business decision to use specific feature changes within that file. If the business chooses to implement these features, uploading the file is required. Otherwise, it's optional.
File name Object API Name Operation Mandatory or Optional Related To Nature of Change
Named_Query_-_NEW_258.csv Sync_Named_Query__c Insert Mandatory DSD sync configuration Records are modified for the DSD process.
Named_Query_-_MODIFIED_258.csv Sync_Named_Query__c Upsert Mandatory DSD sync configuration Records are modified for the DSD process.
Tracked_Object_Config_-_NEW_258.csv Sync_Tracked_Object_Config__c Insert Mandatory DSD sync configuration Records are modified for the DSD process.
Tracked_Object_Config_-_MODIFIED_258.csv Sync_Tracked_Object_Config__c Upsert Mandatory DSD sync configuration Records are modified for the DSD process.
Tour_Check_-_MODIFIED_258.csv cgcloud__Tour_Check__c Upsert Optional DSD We updated SecurityCheck to SafetyCheck for three tour checks.

Upload Hybrid Data Static Resource Files

For hybrid users, download files from RetailHybridData in Static Resources, and then upload the files to Salesforce by using the dataloader.io insert or upsert operation.

Note
Note For more information about unmapped fields that require mapping, see Record Type Mapping. For fields that don’t require mapping, see Unmapped Fields.

Complete the upload of demo data and sync configuration for Retail Execution and Direct Store Delivery.

  1. From Setup, in the Quick Find box, enter Static Resources and select it.
  2. Download and extract the RetailHybridData.zip static resource file.
  3. From Setup, in the Quick Find box, enter Dataloader.io and select it.
  4. Click Launch dataloader.io and login with your org credentials.
  5. In dataloader.io, upload the files from the RetailHybridData/Upgrade/256 folder.

The CSV file that you upload is sometimes dependent on another CSV file. To prevent any errors, we recommend that you upload files in the sequence they are listed in the table.

Important
Important Even if a file upload is marked as optional, the upload depends on the business decision to use specific feature changes within that file. If the business chooses to implement these features, uploading the file is required. Otherwise, it's optional.
File name Object API Name Operation Mandatory or Optional Related To Nature of Change
Named_Query_-_NEW_258.csv Sync_Named_Query__c Insert Mandatory Hybrid sync configuration Records are modified for the hybrid sync configuration.
Named_Query_-_MODIFIED_258.csv Sync_Named_Query__c Upsert Mandatory Hybrid sync configuration Records are modified for the hybrid sync configuration.
Tracked_Object_Config_-_NEW_258.csv Sync_Tracked_Object_Config__c Insert Mandatory Hybrid sync configuration Records are modified for the hybrid sync configuration.
Tracked_Object_Config_-_MODIFIED_258.csv Sync_Tracked_Object_Config__c Upsert Mandatory Hybrid sync configuration Records are modified for the hybrid sync configuration.
Tracked_Object_Config_-_DELETE_258.csv Sync_Tracked_Object_Config__c Delete Mandatory Hybrid sync configuration Records are removed for the hybrid sync configuration.

Upload Route Sales User Data Static Resource Files

For route sales users, download files from RetailRouteSalesData in Static Resources, and then upload the files to Salesforce by using the dataloader.io insert or upsert operation.

Note
Note For more information about unmapped fields that require mapping, see Record Type Mapping. For fields that don’t require mapping, see Unmapped Fields.

Complete the upload of demo data and sync configuration for Retail Execution and Direct Store Delivery.

  1. From Setup, in the Quick Find box, enter Static Resources and select it.
  2. Download and extract the RetailRouteSalesData.zip static resource file.
  3. From Setup, in the Quick Find box, enter Dataloader.io and select it.
  4. Click Launch dataloader.io and login with your org credentials.
  5. In dataloader.io, upload the files from the RetailRouteSalesData folder.

The CSV file that you upload is sometimes dependent on another CSV file. To prevent any errors, we recommend that you upload files in the sequence they are listed in the table.

Important
Important Even if a file upload is marked as optional, the upload depends on the business decision to use specific feature changes within that file. If the business chooses to implement these features, uploading the file is required. Otherwise, it's optional.
File name Object API Name Operation Mandatory or Optional Related To Nature of Change
Sync_Configuration.csv Sync_Config__c Insert Optional Route sales user Records are added for the route sales user persona.
Named_Query.csv Sync_Named_Query__c Insert Optional Route sales user Records are added for the route sales user persona.
Tracked_Object_Config.csv Sync_Tracked_Object_Config__c Insert Optional Route sales user Records are added for the route sales user persona.