DumpIT Installation
Salesforce, Consultants, Crossdoor, Jobs, Freshers, Best Salesforce Consultants India, Salesforce CPQ, Salesforce CTA
308
page-template,page-template-full_width,page-template-full_width-php,page,page-id-308,page-child,parent-pageid-275,bridge-core-1.0.5,ajax_fade,page_not_loaded,,qode-title-hidden,qode_grid_1300,qode-theme-ver-18.1,qode-theme-bridge,disabled_footer_bottom,wpb-js-composer js-comp-ver-6.0.2,vc_responsive
Prerequisites

Before DumpIT can be installed you will need Java installed on your local machine. If you already have Java on your computer, you don’t need to install, so first verify the installation from a command prompt.Java version 1.7.x or later is recommended for better security and for the latest TLS security protocols.

To check the version of Java that’s installed on your system:

  1. Open a command prompt.
  2. At the prompt, type java -version and press Enter.
  3. If you have Java version 7, the output looks something like the following:
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)

To install Java, go to http://www.oracle.com/technetwork/java/javase/downloads/index.html and get the latest version of the Java JDK. When you’re finished with the installation, verify by typing java -version at a command prompt.

Setup

Follow these steps to download and install DumpIT:

  1. Make sure that Java is installed on your local machine.
  2. Download the latest version of the zip file.
  3. Extract the zip file locally on your machine.
  4. The extracted contents of the zip file will have the following files and folders:

DumpIT folder

  1. build.properties file. This is the file where you will configure the tool.
  2. DumpIT.jar file. The jar file name will have the version number in it.
Configuring

Make sure you have downloaded the latest version and followed the pre-requisites steps before DumpIT can be used. Follow these steps to use the tool:

Configure build.properties
source.username Salesforce username for the source org from which the data will be picked and copied into a target Org. Make sure the user at-least has “View All Data” permission. Preferably user should have System Administrator profile.
source.password The password for source Salesforce Org. If security token is required, append it along with the password.
source.serverURL Salesforce server URL for the source Org. Use https://login.salesforce.com for production and developer Orgs and https://test.salesforce.com for Sandbox Org.
target.username Salesforce username for the target org where the data will be copied. Make sure the user has “Modify All Data” permission. Preferably user should have System Administrator profile. There are few features which only works while using the standard System Administrator profile.
target.password The password for target Salesforce Org. If security token is required, append it along with the password.
target.serverURL Salesforce server URL for the target Org. Use https://login.salesforce.com for production and developer Orgs and https://test.salesforce.com for Sandbox Org.
process.objects Comma separated list of object API names. Data for objects listed here will only be copied. The sequence in which the objects are listed is important as the tool inserts records in the given sequence only. Make sure all the parents are listed before the child objects.
<ObjectAPIName>.where Replace the objectAPIName with the API name of the object for which you want to filter the records. Add the where clause similar to what you would add in a SOQL. Make sure the equals sign is escaped by using a back slash. Example if you want to copy only hot rated Accounts with industry set to IT, you would add the condition as:
Account.where = Rating\= ‘Hot’ AND Industry \= ‘Information Technology’
process.statusOutputDirectory Set the path of the folder where the resultant success and error csv files will be generated for each object. Make sure the path ends with a back slash.
Run the tool

Now that you have configured the build.properties you are ready to see the tool in action.

  1. Open command prompt/terminal.
  2. Go to DumpIT folder (the one with build.properties and jar file).
  3. Run this command, change the name of the jar file based on the jar version file you have downloaded.

java -jar DumpIT4.jar

CPQ Deployment

Majority of the Salesforce CPQ implementation is data driven i.e. you configure CPQ by setting Products, Products Options, Price Rules, Product Rules and so on. One of the biggest CPQ challenge is deploying what you have done in a developer Sandbox into QA / UAT Sandbox and finally into Production.

A great amount of time goes into setting these data items again in another Salesforce Org or Sandbox. You can use DumpIT to make this task easier and quicker.

Here is a sequence of commonly configured CPQ objects (template) which you can use with DumpIT. Set them in your build.properties and relax. Here is the template you can use:

process.objects = Pricebook2, Product2, PricebookEntry, PricebookEntry, SBQQ__DiscountSchedule__c, SBQQ__DiscountTier__c, SBQQ__BlockPrice__c, SBQQ__Cost__c, SBQQ__ProductFeature__c, SBQQ__ProductOption__c, SBQQ__ConfigurationAttribute__c, SBQQ__SummaryVariable__c, SBQQ__ProductRule__c, SBQQ__ProductAction__c, SBQQ__ErrorCondition__c, SBQQ__ConfigurationRule__c, SBQQ__PriceRule__c, SBQQ__LookupQuery__c, SBQQ__PriceAction__c, SBQQ__CustomAction__c, SBQQ__CustomActionCondition__c, SBQQ__SolutionGroup__c, SBQQ__ImportFormat__c, SBQQ__TemplateContent__c, SBQQ__QuoteTemplate__c, SBQQ__TemplateSection__c, SBQQ__LineColumn__c,SBQQ__QuoteTerm__c, SBQQ__QuoteTerm__c, SBQQ__TermCondition__c, SBQQ__QuoteProcess__c, SBQQ__ProcessInputCondition__c, SBQQ__ProcessInput__c
Advance Approvals Deployment

Similar to CPQ Deployments, Advance approval configuration is also data dependent.  Here is a sequence of advance approval objects (template) which you can use with DumpIT:

process.objects = sbaa__EmailTemplate__c, sbaa__ApprovalVariable__c, sbaa__ApprovalVariable__c, sbaa__Approver__c, sbaa__Approver__c, sbaa__ApprovalChain__c, sbaa__ApprovalRule__c, sbaa__ApprovalCondition__c, sbaa__Approval__c

Advance approval configuration requires setting hard coded Ids as texts at various differet places, these Ids have to be manually updated in the target Org, once the deployment is done.