Loading
Set Up and Maintain Retail Execution
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Additional Steps to Upgrade Managed Packages to Summer ’25

          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

          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/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
            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
          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 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
          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
          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 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
          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.
           
          Loading
          Salesforce Help | Article