Legacy:Salesforce:Custom Batch Processing: Difference between revisions

From Melissa Data Wiki
Jump to navigation Jump to search
Created page with "← Clean Suite for CRM:Salesforce {{CustomTOC}} ==Custom Batch Processing== ''Note: This section is for advanced salesforce users/devel..."
 
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Clean Suite for CRM:Salesforce|← Clean Suite for CRM:Salesforce]]
{{LegacyListwareForSalesforceNav
|VisualforceCollapse=
}}
 
{{CustomTOC}}
{{CustomTOC}}


Line 13: Line 16:
The part highlighted in cyan is the SOQL query and is how they specify what subset of records need to be processed. When SELECTing the fields, '''you must SELECT all the fields that mapped under the “Listware Advanced Mappings” tab for both the input and output.''' You can run the SOQL query:
The part highlighted in cyan is the SOQL query and is how they specify what subset of records need to be processed. When SELECTing the fields, '''you must SELECT all the fields that mapped under the “Listware Advanced Mappings” tab for both the input and output.''' You can run the SOQL query:


<pre>SELECT MDPERSONATOR__inputMap__c, MDPERSONATOR__outputMap__c FROM MDPERSONATOR__MD_customMappings__c</pre>
<pre class="indent">SELECT MDPERSONATOR__inputMap__c, MDPERSONATOR__outputMap__c FROM MDPERSONATOR__MD_customMappings__c</pre>


and see the API names of the fields that were mapped in.
and see the API names of the fields that were mapped in.

Latest revision as of 01:14, 13 January 2022

← Legacy:Clean Suite for CRM:Salesforce

Legacy Salesforce Navigation
Introduction
Getting Started
Installation
Setup
Credits
Components
Express Entry Component
Visualforce Pages
Installing Visualforce Pages
Custom Visualforce Pages
Batch Processing
Custom Batch Processing
Legacy Result Codes
Salesforce Result Codes



Custom Batch Processing

Note: This section is for advanced salesforce users/developers. Before proceeding, it is recommended that you have a fundamental grasp of SOQL and are comfortable with APEX code. Make sure all settings are correct before running a batch job, as batch jobs can result in unexpected record processing if not careful.

Starting a Batch Job

An example of how to start up a batch job:

Id batchinstanceId = Database.executeBatch(new MDPERSONATOR.MD_PersonatorBatch('SELECT FirstName, LastName, MailingStreet, MailingCity, MailingCountry, MailingPostalCode, MailingState, Email, Phone, MailingLatitude, MailingLongitude FROM Contact', true, true), 100);

SOQL Query

The part highlighted in cyan is the SOQL query and is how they specify what subset of records need to be processed. When SELECTing the fields, you must SELECT all the fields that mapped under the “Listware Advanced Mappings” tab for both the input and output. You can run the SOQL query:

SELECT MDPERSONATOR__inputMap__c, MDPERSONATOR__outputMap__c FROM MDPERSONATOR__MD_customMappings__c

and see the API names of the fields that were mapped in.

Boolean Parameters

The part highlighted in purple are two Boolean parameters. The first one, if set true, will tell the batch process to update the Salesforce records with the clean/standardized data using the output mapping specified in Listware. The second one, if set true, will process all records returned by the SOQL query regardless of whether the record has been processed before using Listware.

Fixed Setting

The last part, highlighted in yellow, should always be left to 100 and should not be adjusted.