Tutorials

  1. Home
  2. Dokumente
  3. Tutorials
  4. 89. How to push data to the Database using the new Agent
  5. 89.2 How to do update operation using Synchronous and Asynchronous outbound interface?

89.2 How to do update operation using Synchronous and Asynchronous outbound interface?

Introduction

This tutorial will guide you on how to send data in multiple objects from Salesforce to the multi-table in the database as synchronously and asynchronously through Agent V3 or Any Connect. We will know about Transactional and Non-Transaction mode during processing, Using mapping in WHERE condition. MYSQL Database is used for example to modify the existing records in the database and it located on EC2 instance.

Pre-required 

  • Create a Repository and generate Message Type from the database
  • Modify message type for adding a field in WHERE-Clause
  • Using Mapping tool in WHERE condition
  • Create an outbound Interface and checking Cache monitoring status
  • Callout V3 to new Agent
  • Transactional and None-Transactional mode

How to do update operation using a Synchronous outbound interface?

In this example, we use the same Database Adapter in the previous section as it used for INSERT operation. Now we use that Adapter for UPDATE operation.

Step-1: create another Repository for Update operation and then generate Message Type from the database

  • Fill all required field then click Retrieve Database to get the Table’s record
    • Agent Instance: your instance name
    • Adapter Name: your adapter name
    • Object Type: Table, View, Procedure
    • Database Operation: Update (database’s template will be generated base on operation)
  • Choose Table’s name for creating Message Type
  • After that, we got the Message Type generated from the database
  • Here the example for Table called: “tbl_account_db_atn
    Note
    For Update/Delete operation, we have a template for generating Message Type for a single Table
    – Create Messages Type as a child of the root with fixed name “Request” within type as “Database Request”.
    – Under “Request”, create a Message Type as the child. The Table’s name is used for this Message Type within type as “Database Table”. i.e: tbl_account_db_atn. In this Message, Type was generated the field name like on Table. Two Message Type has been generated for this Message Type as the child with the fixed name: WHERE-Clause type as “Database WHERE Clause” and WHERE-Expression type as “Database WHERE Expression”. In WHERE-Expression has been generated the fixed field name that is “Expression” for putting condition value.

    Currently, we need to manual re-order Message Type as the parent and child. As the example below, we have three Message Type refer to three Tables on the database. Under “Request” we take “tbl_account_db_atn” as the parent of “tbl_contact_db_atn and tbl_case_db_atn” as the child of “tbl_contact_db_atn”, these Message Type are Database Table type.In WHERE-Clause Message Type, we did not generate any field from the Table because we never use all the fields on the table in the condition. The user needs to add a field on WHERE-Clause for using in the condition by going to WHERE-Clause which relevant to its parent Message Type then navigate to Related tab => Select Field From Repository

    In this example below is showing WHERE-Clause on tbl_account_db_atn. For another Message Type like tbl_contact_db_atn and tbl_case_db_atn is the same step scenario for adding the field on WHERE-Clause.

  • At this point, we need to choose the Metadata Provider and Repository name and then select the field that we need put in the condition.
  • After click Save, we got some fields below

Step 3: Set up Interface

Define the Request Interface

  • Create an outbound Interface for Synchronous mode, operation(update), choose  Adapter, Metadata Provider, Repository, and Message Type (Request)
  • On the Interface details page, click the button Open Mapping

In the mapping tool, we map it followed to the standard UPDATE statement with WHERE-Clause.

UPDATE table_name

SET column1 = value1, column2 = value2, …

WHERE condition;

Mapping scenario example:

  • We map “Account” sObject to node “tbl_account_db_atn”: to define which Table for update
  • “Description” to “Description” of node “tbl_account_db_atn”: to define which field of the Table use in condition for the update.
  • “Id” to “SF_AccountId” of node WHERE-Clause: to define the condition field’s name.
  • “Functions” to “Expression” of node WHER-Expression: to define the condition field’s value. After mapping, this field, the Formula and Expression’s form will be pop up. We can also map another field to Expression, then check the Formula flag

After do mapping, the SQL Update statement is to look like the example below:

    • UPDATE tbl_account_db_atn SET Description WHERE SF_AccountId = …..
    • UPDATE tbl_contact_db_atn SET Description WHERE SF_ContactId = …..
    • UPDATE tbl_case_db_atn SET Description WHERE SF_CaseId = … AND DB_CaseID = ‘963’
Note

In WHERE-Expression, we need to put the question mark (?) for getting dynamic value from the field that presents in the WHERE-Clause. We can put the static value in WHERE-Expression unless that field did not present in WHERE-Clause. If we put the static value for the field that comes from WHERE-Clause then we will be getting the incorrect expected result. The static value must be inside the quote symbol.

For the example below the field “SF_CaseId” presents in WHERE-Clause, so we need to put “?” . And field “DB_CaseId” did not present in WHERE-Clause, so we can put static value.

Step- 4: Checking Cache record to ensure it synchronized to new Agent.

  • Go to Agent control board then click Cache Monitor

 

Step 5: Callout V3

Navigate to Setup gear icon => Developer Console => Debug menu => Open Execute Anonymous Window then put code for update Account object then click the Execute button.

skyvvasolutions.CallOutControl c = new skyvvasolutions.CallOutControl();
c.returnJSONComplete=true;
c.actionDoIntegrate=true;
c.isCreateMessage=true;
String[] ids= new String[]{‘0013E00001CxX5NQAV’};
skyvvasolutions.Iservices.invokeCalloutV3(‘Test MYSQL-Database Integration’,’MYSQL_Database_InternalKEY_Update_SYNC_Multi table’,ids,’SYNC’,c);
  • After callout, the record is update completely into the database base on condition.  As shown the result on Message monitoring below:

 

  • Check Result on database, the record is updated correctly in MYSQL database
    • The field “Description” on Table “tbl_account_db_atn” is updated correctly

  • The field “Description” on Table “tbl_contact_db_atn” is updated correctly

  • The field “Description” on Table “tbl_case_db_atn” is updated correctly. Because the condition is met only one record, so other records not affected.

How to do update operation using an Asynchronous outbound interface?

In this example, we use the same Interface as we have practiced for the Synchronous scenario, just change the processing mode to Asynchronous on Interface then Callout v3.

Note

For Asynchronous mode with Outbound Interface is a dependency on the field “Transfer Package Size” on the Interface. By default, this field is blank mean that the value “1”. The calculation of API call is depending on this field.

For example, in case we are sending 3 records Account’s id:

  • If “Transfer Package Size=2”, it will execute 2 API call.
  • If “Transfer Package Size=1”, it will execute 3 API call.
  • Callout v3

Navigate to Setup gear icon => Developer Console => Debug menu => Open Execute Anonymous Window then put code for update Account object then click the Execute button.

skyvvasolutions.CallOutControl c = new skyvvasolutions.CallOutControl();
c.returnJSONComplete=true;
c.actionDoIntegrate=true;
c.isCreateMessage=true;
String[] ids= new String[]{‘0013E00001CxX5NQAV’};
skyvvasolutions.Iservices.invokeCalloutV3(‘Test MYSQL-Database Integration’,’MYSQL_Database_InternalKEY_Update_SYNC_Multi table’,ids,’Auto’,c);
Note
if your data contain much more, so you cannot process it by Synchronous call due to the request time out error, we need an Asynchronous. In the Asynchronous call, multi-task does at the same time in the background job, the user no need to wait to see the response back. In this case, Agent will be responding to update message Complete or Failed for a while.

Checking result on Message monitoring, the record is update completely and the Agent has been updated the message to complete.

Update operation and Transactional mode

Normally, when we creating a new Interface the field “isTransactional” is unchecked it means that Non- Transactional Mode. If that field is checked then it is Transactional mode.

Note
Transactional Mode: If any error while update of one message then the complete message will be rollback with marking failed for the complete message.
Non-transactional Mode: If any error while update of one message then the respective message will be marked as failed
These two modes are to support both Interface processing Synchronous and Asynchronous.

The example below has shown the Non-transactional Mode which is one message on the last level is failed to update.

 

The example below is used the same message scenario for Non-transactional Mode, it just switching to Transactional Mode. In Transactional Mode, when one message is unable to do any database operation then it makes another message which is complete to rollback and marked the whole tree as Failed status.

  • For Synchronous mode, the Agent will return only the root message status.

  • For Asynchronous mode, the Agent will return the whole tree message status.

Summary

Finally, we have learned about how to do update operation using Synchronous and Asynchronous outbound interface. We have understood about Message Type in WHERE-Clause, knowing about putting value in WHERE-Clause on mapping tool, and callout v3 to Agent. And we also have known about Transactional Mode.

Fandest du diesen Artikel hilfreich? Ja Nein

Wie können wir helfen?