In SKYVVA, the bulk-loading option increases the performance of a session where huge volumes of data are involved. During bulk loading, the Integration Service bypasses the database log, which results in performance improvement. Without writing to the database log, however, the target database cannot perform a rollback. While using bulk loading, the need for improved session performance must be weighed against the ability to recover an incomplete session.
we are talking about the SKYVVA bulk mode and not the SFDC bulk mode. The significant change we make is not using the attachment object anymore to store the json payload. We are using file and link the file to the interface. Thus we will have two solution parallel running e.g. using the attachment with V2 and Files with V3. Our scheduler can check the type of the Salesforce Id and know if it is an attachment or File object. Based on this fact we will enter the old or new processing
We will not build a new scheduler but change the existing scheduler to process both variant e.g. attachment and file. The scheduler needs to read now from both sources e.g. attachment or files and processes either attachment or files depending on what it can find.
Prerequisite #
– Create Meta Data Provider
– Create Integration and inbound Interface
– Push data payload from SoapUI with API : …/V3/Integrate
1- Create Meta Data Provider,
2- Create IStructure Repository and MessageType
(i.e. AccountTestV3, ContactTestV3, CaseTestV3)
In this case we use Open Editor on Repository to create Message Type
<?xml version=”1.0″ encoding=”UTF-8″ standalone=”no”?>
<AccountTestV3>
<AccountNumber>10001</AccountNumber>
<Name>TestAccount1</Name>
<BillingCountry>Cambodia1</BillingCountry>
<BillingCity>Phnom Penh1</BillingCity>
<Account_ID>A-001</Account_ID>
</AccountTestV3>
</Root>
Difference Between SKYVVA Bulk and SFDC Bulk Mode? #
SKYVVA Bulk Mode | SFDC Bulk Mode |
In SKYVVA Bulk Mode user can create upsert, update, insert, and query, query All, pullQuery or delete a large volume of records with the Bulk API, which is optimized for processing large sets of data. It makes it simple to load, update, or delete data over a 5000 records. | In SFDC Bulk Mode user can create update, or delete a large volume of records with the Bulk API, which is optimized for processing large sets of data. It makes it simple to load, update, or delete data from a few thousand to millions of records. |
Monitoring in Bulk Control Board: As user did integrate, your data you might want to check or monitor if all your data are successfully integrated. To monitor bulk data. There are three orders to monitor bulk processing: Bulk Data Inbox : When data pushed from the client using Bulk API, that will appear in this section Bulk Data Processing: Bulk Data Processing is using to store data that are processing. Bulk Monitor: User can monitor the total records of attachments, total batch and batches that had processed. |
Monitoring Bulk Data Load Jobs: Process a set of records by creating a job that contains data that will be processed asynchronously. The job specifies which object is being processed and what type of operation is being used. |
Indexes, constraints, auto-generated features can be available in table level during the job run.
Operations:
It support SFDC BulkV1.0,SFDCV2.0 for all Job Type |
Operations:
hardDelete (Bulk V1 type jobs only) |