---
schema_version: "1"
id: f2f94ae2d2e3477ec11499585d30392692962fdfd4446b5cce737336a7290be9
title: Additional Steps to Upgrade Managed Packages to Spring ’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_254.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.cg_concept_admin_static_resources_upgrade_254.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3013cc9508611a445a6246ab3067248e88890b14638fc9c0af25cff05469d70c
description: To upload demo data for Spring ’25, perform these steps.
products:
- Consumer Goods
release: "264"
---
# Additional Steps to Upgrade Managed Packages to Spring ’25
To upload demo data for Spring ’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/252 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 |
| --- | --- | --- | --- | --- | --- |
| Sales\_Organization\_-\_MODIFIED\_254.csv | Sales\_Organization\_\_c | Upsert | Optional | Direct Store Delivery (DSD) Demo data | Records are modified for geofencing validation. |
| Order\_Item\_Template\_-\_MODIFIED\_254.csv | Order\_Item\_Template\_\_c | Upsert | Optional | Direct Store Delivery (DSD) Demo data | Records are modified for the DSD process. |
| Order\_Item\_Template\_-\_NEW\_254.csv | Order\_Item\_Template\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Signature\_Template\_-\_254\_NEW.csv | Signature\_Template\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Signature\_Template\_-\_MODIFIED\_254.csv | Signature\_Template\_\_c | Upsert | Optional | Direct Store Delivery (DSD) Demo data | Changes to picklist values for the Attribute Set field. |
| Signature\_Flow\_Step\_-\_NEW\_254.csv | Signature\_Flow\_Step\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| System Setting - NEW 254.csv | System\_Setting\_\_c | Insert | Optional | Agentforce and Einstein generative AI | New records are added for generative AI and Agentforce features. |
| Mobile\_App\_Domain\_-\_NEW\_254.csv | Sync\_Mobile\_App\_Domain\_\_c | Insert | Mandatory | Direct Store Delivery (DSD) Demo data | New records are added for geofencing validation. |
| Mobile\_App\_Picklist\_Mapping\_-\_NEW\_254.csv | Sync\_Mobile\_App\_PL\_Map\_\_c | Insert | Mandatory | Direct Store Delivery (DSD) Demo data | New records are added for geofencing validation. |
| Mobile\_App\_Picklist\_Mapping\_Extension\_-\_NEW\_254.csv | Sync\_Mobile\_App\_PL\_Map\_Ext\_\_c | Insert | Mandatory | Direct Store Delivery (DSD) Demo data | New records are added for geofencing validation. |
| Mobile\_App\_Picklist\_Mapping\_Extension\_-\_MODIFIED\_254.csv | Sync\_Mobile\_App\_PL\_Map\_Ext\_\_c | Upsert | Mandatory | Direct Store Delivery (DSD) Demo data | Records are modified for DSD and geofencing validation. |
| Tracked Object Config\_-\_MODIFIED\_254.csv | Sync\_Tracked\_Object\_Config\_\_c | Upsert | Mandatory | Direct Store Delivery (DSD) Demo data | Records are modified for geofencing validation. |
| Order\_Template\_-\_NEW\_254.csv | Order\_Template\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Order\_Template\_-\_MODIFIED\_254.csv | Order\_Template\_\_c | Upsert | Optional | Direct Store Delivery (DSD) Demo data | Records are modified for the DSD process. |
| Order\_Item\_Order\_Template\_Association\_-\_NEW\_254.csv | Order\_Item\_Order\_Template\_Association\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Order\_Template\_Product\_Selector\_Group\_-\_NEW\_254.csv | Order\_Template\_Product\_Selector\_Group\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Inventory\_Control\_Template\_-\_NEW\_254.csv | Inventory\_Control\_Template\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Order\_Template\_Order\_Payment\_Template\_254\_NEW.csv | Order\_Template\_Order\_Payment\_Template\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
| Order\_Item\_Inventory\_Transaction\_-\_NEW\_254.csv | Order\_Item\_Inventory\_Transaction\_\_c | Insert | Optional | Direct Store Delivery (DSD) Demo data | New records are added for the DSD process. |
## Upload Penny Perfect Pricing Static Resource Files
To use the Penny Perfect Pricing feature, download files from RetailPPPData in Static Resources, and then upload the files to Salesforce by using the dataloader.io insert or upsert operation.
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 RetailPPPData.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 file from the RetailPPPData/Upgrade/252 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.
If you upload the Order\_Item\_Template\_-\_MODIFIED\_254.csv file from both the RetailRepositoryData and RetailPPPData folders, it can lead to duplication of records. Upload the file only if you haven’t uploaded it from the RetailRepositoryData folder.
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 |
| --- | --- | --- | --- | --- | --- |
| Order\_Item\_Template\_-\_MODIFIED\_254.csv | Order\_Item\_Template\_\_c | Upsert | Optional | Direct Store Delivery (DSD) Demo data | Modification Reason values are modified for the DSD process. |
## 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/252 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\_254.csv | Sync\_Tracked\_Object\_Config\_\_c | Upsert | Mandatory | DSD Sync Configuration | Records are modified to adopt the geofencing validation. To identify the tracked objects that are modified, use the Object API Name column. |