---
schema_version: "1"
id: 2a7de2fe0cbc9014668e697d03f6e83aacc0fd10e3e464b0f75c7a0b3927e710
title: Additional Steps to Upgrade Managed Packages to Summer ’25
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/cg_concept_admin_static_resources_upgrade_256.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.cg_concept_admin_static_resources_upgrade_256.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ae37e249cc3a7ca55227000091164bbf2a464c5019c8bae4be1c6ba0b3c04da4
description: To upload demo data for Summer ’25, perform these steps.
products:
- Consumer Goods
release: "264"
---
# Additional Steps to Upgrade Managed Packages to Summer ’25
To upload demo data for Summer ’25, 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](https://help.salesforce.com/s/articleView?id=ind.cg_task_handle_validation_rules.htm&type=5&language=en_US)
Note For more information about unmapped fields that require mapping, see [Record Type Mapping](https://help.salesforce.com/s/articleView?id=ind.cg_concept_admin_map_recod_types.htm&release=264.0.0&type=5 "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."). For fields that don’t require mapping, see [Unmapped Fields](https://help.salesforce.com/s/articleView?id=ind.cg_concept_admin_unmap_record_types.htm&type=5&language=en_US).
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/254 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 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 |
| --- | --- | --- | --- | --- | --- |
| Custom\_Permission\_User\_Role\_Mapping\_-\_NEW\_256.csv | Custom\_Permission\_User\_Role\_Mapping\_\_c | Insert | Mandatory | Hybrid persona | Custom permission record is added to user role mapping for hybrid user persona. |
| Order\_Template\_-\_MODIFIED\_256.csv | Order\_Template\_\_c | Upsert | Optional | Direct Store Delivery (DSD) Demo data | Records are modified to add hybrid user role in user roles for DSD related order templates. |
| Order\_Template\_Product\_Selector\_Group\_-\_NEW\_256.csv | Order\_Template\_Product\_Selector\_Group\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Order\_Item\_Template\_-\_MODIFIED\_256.csv | Order\_Item\_Template\_\_c | Upsert | Optional | Direct Store Delivery (DSD) Demo data | Records are modified for the DSD process. |
| Inventory\_Control\_Template\_-\_NEW\_256.csv | Inventory\_Control\_Template\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Order\_Payment\_Template\_-\_NEW\_256.csv | Order\_Payment\_Template\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | Records are added for the DSD process. |
| Order\_Payment\_Inventory\_Transaction\_-\_NEW\_256.csv | Order\_Payment\_Inventory\_Transaction\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Order\_Template\_Order\_Payment\_Template\_-\_MODIFIED\_256.csv | Order\_Template\_Order\_Payment\_Template\_\_c | Upsert | Optional | Direct Store Delivery (DSD) Demo data | Records are modified for the DSD process. |
| Named\_Query\_-\_DELETE\_256.csv | Sync\_Named\_Query\_\_c | Delete | Mandatory | First sync of the day (FSOD) | Removed the ValidStdJobDefinitionLists Named Query. |
| Named\_Query\_-\_MODIFIED\_256.csv | Sync\_Named\_Query\_\_c | Upsert | Mandatory | First sync of the day (FSOD) | Updated the StdJobDefinitionListsWithoutCust Named Query. |
## 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.
Make sure to upload demo data and complete the sync configuration for Retail Execution.
Note For more information about unmapped fields that require mapping, see [Record Type Mapping](https://help.salesforce.com/s/articleView?id=ind.cg_concept_admin_map_recod_types.htm&release=264.0.0&type=5 "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."). For fields that don’t require mapping, see [Unmapped Fields](https://help.salesforce.com/s/articleView?id=ind.cg_concept_admin_unmap_record_types.htm&type=5&language=en_US).
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/254 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 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 |
| --- | --- | --- | --- | --- | --- |
| Tracked\_Object\_Config\_-\_MODIFIED\_256.csv | Sync\_Tracked\_Object\_Config\_\_c | Upsert | Mandatory | DSD Sync Configuration | Records are modified for the DSD process. |
## 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.
Complete the upload of demo data and sync configuration for Retail Execution and Direct Store Delivery.
Note For more information about unmapped fields that require mapping, see [Record Type Mapping](https://help.salesforce.com/s/articleView?id=ind.cg_concept_admin_map_recod_types.htm&release=264.0.0&type=5 "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."). For fields that don’t require mapping, see [Unmapped Fields](https://help.salesforce.com/s/articleView?id=ind.cg_concept_admin_unmap_record_types.htm&type=5&language=en_US).
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 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 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 | Hybrid user | Records are added for the hybrid persona. |
| Named\_Query.csv | Sync\_Named\_Query\_\_c | Insert | Optional | Hybrid user | Records are added for the hybrid persona. |
| Tracked\_Object\_Config.csv | Sync\_Tracked\_Object\_Config\_\_c | Insert | Optional | Hybrid user | Records are added for the hybrid persona. |