Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Energy & Utilities Cloud
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
          Troubleshoot Static Resources Migration for Customer Acquisition Management

          Troubleshoot Static Resources Migration for Customer Acquisition Management

          Troubleshoot issues that can occur when you migrate Customer Acquisition Management datapacks to your Salesforce org.

          Error deploying EPC datapack

          While deploying EPC datapack, you may get an error that reads

          PricingPlan/Default Pricing Plan - Invalid pricing plan implementation name: CustomPricingPlanStepImpl

          To solve this problem, deploy the SFDX apex classes first and then deploy the EPC datapack.

          Errors while deploying SFDX components that reads "No Network named VEE Digital Sales found"

          To solve this problem, while deploying SFDX components, select network, siteDotComSites, and sites, then deploy them together.

          Errors while deploying SFDX components that reads "Apex class 'CommunitiesLandingController' does not exist"

          To solve this problem, copy the following Apex Class files to the sfdx/classes folder on your system, and then deploy them.

          Error while deploying Vlocity components "This Expression Set Version already exists in Active state, Please create a new version and try again"

          You get an error that reads:

          Error: Could not process MDAPI response: Update of ExpressionSetDefinition VEEDCSalesPricingProcedure: Error: This Expression Set Version already exists in Active state, Please create a new version and try again.
          

          The error may be caused if the VEEDCSalesPricingProcedure ExpressionSetDefinition components are already available in the org.

          To solve this problem, skip deploying the VEEDCSalesPricingProcedure ExpressionSetDefinition component.

           
          Loading
          Salesforce Help | Article