Deprecated: Optional parameter $list declared before required parameter $is_script is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 21

Deprecated: Optional parameter $register declared before required parameter $footer_or_media is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 45

Deprecated: Optional parameter $register declared before required parameter $footer_or_media is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_cdn.php on line 104

Deprecated: Optional parameter $expire declared before required parameter $path is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/class.redux_functions.php on line 54

Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/themes/entaro/inc/classes/megamenu.php on line 155

Deprecated: Optional parameter $depth declared before required parameter $output is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/themes/entaro/inc/classes/mobilemenu.php on line 147

Deprecated: Optional parameter $args declared before required parameter $wp_customize is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/extensions/customizer/extension_customizer.php on line 583

Deprecated: Optional parameter $args declared before required parameter $wp_customize is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/extensions/customizer/extension_customizer.php on line 606

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/switch/field_switch.php on line 17

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/switch/field_switch.php on line 17

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/media/field_media.php on line 46

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/media/field_media.php on line 46

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/select/field_select.php on line 17

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/select/field_select.php on line 17

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/editor/field_editor.php on line 46

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/editor/field_editor.php on line 46

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/text/field_text.php on line 17

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/text/field_text.php on line 17

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/slider/field_slider.php on line 40

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/slider/field_slider.php on line 40

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/radio/field_radio.php on line 17

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/radio/field_radio.php on line 17

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/info/field_info.php on line 45

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/info/field_info.php on line 45

Deprecated: Optional parameter $field declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/typography/field_typography.php on line 50

Deprecated: Optional parameter $value declared before required parameter $parent is implicitly treated as a required parameter in /home1/oijoiv2f/public_html/wp-content/plugins/apus-framework/libs/redux/ReduxCore/inc/fields/typography/field_typography.php on line 50
How to use Jitterbit Cloud agent with Salesforce - Salesforce Next Gen
Jitterbit Cloud agent with Salesforce

How to use Jitterbit Cloud agent with Salesforce

How to use Jitterbit Cloud agent with Salesforce

Jitterbit Cloud agent with Salesforce

Have you ever found yourself in a situation/requirement where you need to extract the data from Salesforce and either create a flat file (.csv or .txt) or connect it to an external file server and directly save file there?  For Start salesforce does not provide any native tool to write a file directly to external/ local machines, you would either have to create a custom VF page, load the content there and then convert it to flat file version, the Salesforce does not support FPT connection- there are some workaround but they are very limited and sometimes does not meet the requirements.

To perform the basic task of Extract, Transform and Load, the first third party tool which comes to mind to many salesforce developers is Jitterbit cloud data loader. It is a free tool (Not as powerful as the paid version, but it does the trick). This tool is very easy to use and is one of the most basic one.

To further understand how the integration is done between these two platforms, you require the following:

  1. Salesforce developer edition.
  2. Jitterbit Cloud data loader agent installed on your local machine
  3. Account with Jitterbit Cloud Data loader

Jitterbit data loader can be downloaded from the following link:

https://www.jitterbit.com/solutions/salesforce-integration/salesforce-data-loader/

Create an account on Jitterbit and login to the application.

Below is the screenshot of login screen

Salesforce Jitterbit

Once you successfully login to the data loader the home screen looks like as below.

Salesforce Jitterbit

At the home screen you see the basic task like Query, upsert, insert, update delete and bulk process, to begin with you click on any one of the process and it will next prompt you to login with your salesforce credentials. You need to know your security token to go further, you receive security token when your account is created, or you can reset your security token in my personal information section in the salesforce.

Next step is to select the object, whose record you want to fetch from the salesforce server.

Salesforce Jitterbit

Once you select the object and click next button, it will then provide you with a query building tool where you can either write a query yourself or you can select the fields you want to include in the result as shown below.

Salesforce Jitterbit

This query builder works similar to the query builder provided by the salesforce. Once you have built your query, you can test the output of that query by clicking on the test query button, it will open a query result window which will give you a snapshot of the result your query is going to provide, as shown below.

Salesforce Jitterbit

Once you are good with the query result, you then click on next and it will take you to the next step which is “Where you want to put your data”, i.e. at a local machine or at a ftp server as shown below.

Salesforce Jitterbit

Based up on your select the next steps will vary. Let select local File for now. At this step it also ask you for an option to transform your data, i.e. a target file structure, for this purpose you can either buid you file from scratch or if you have a target file structure you can upload it directly and Jitterbit will create a target file structure on your behalf.

Provide the name of the file format and provide the location path where you want the resulting file to be stored. You can provide a custom name for the resulting file.

Salesforce Jitterbit

Once you have selected the target file location, Jitterbit will ask you to provide the format of the file i.e. data type of each fields as below.

Here you can either use the resulting query to be the format or you can build your own format or you can upload a structure as mentioned in the earlier step.

Salesforce Jitterbit

Next Jitterbit asks you to automate this event, i.e. run this at a particular schedule as shown below.

Salesforce Jitterbit

As soon as you click on finish, it will schedule the operation to run on the specified schedule and take you to a transformation screen where you can map the salesforce field with resulting columns of the target file as shown below.

Salesforce Jitterbit

Once you are finished with mapping click on the finish button below and Jitterbit will now take you to the operation overview screen where you can have all the information about the process at one place as shown below.

Salesforce Jitterbit

To test the query instantly you can click on the run query button and the query will fetch the data and depending upon your selection of the target location a new file would be created at the specified location.

Also, Have a look at the below resources:

  1. Best Salesforce Interview Questions book with Apex and Visualforce concept explained

Also, Have a look at the below learning resources:

  1. SOQL (Salesforce Object Query Language)

  2. Apex Trigger Best Practices and the Trigger Framework

  3. Salesforce Interview Question and Answers Part 2

  4. Salesforce Interview Questions on Test Class

  5. Salesforce-lightning-interview-questions-2018

     6. Salesforce Interview Questions Batch Clas

Sumit Datta

Sumit Datta

I am a 5x Certified Salesforce developer with overall 7 years of IT experience and 5 years of Implementation experience in Salesforce. I am here to share my knowledge and help Beginners in Salesforce to understand the concepts of Apex, Visualforce, Salesforce Lightning and Salesforce Configuration.

Leave a Comment

Your email address will not be published.