4. How to execute a callout CSV payload for V3 Hierarchical has multiple Levels?

Integration with Skyvva: Ensure that your CSV payload aligns with the data model requirements of SKYVVA. Users need to configure mappings, transformations, and integration settings within the SKYVVA platform.

Define the integration flow, including the source (Internet Drive Adapter) and target (V3 Outbound Adapter).
Map fields between the source and target to ensure data is correctly transferred.

CSV Payload of V3 Outbound Adapter for Hierarchy: To support hierarchy in your CSV payload, users must consider using a nested or flat structure with reference identifiers. Here's an example using a nested structure:

[su_box title="CSV" box_color="#2a8af0" title_color="#000000"]ParentID,ParentName,ChildID,ChildName 1,Parent1,101,Child1A 1,Parent1,102,Child1B 2,Parent2,201,Child2A[/su_box]

It shows, that ParentId and ChildId establish the hierarchy, and you can have additional columns for other attributes.

Use Case: The Internet Adapter can execute a callout with a CSV payload for the V3 hierarchy has Multiple Levels

To accommodate the generation of child records with V3 hierarchical data in CSV file format, users have decided to introduce a node prefix when the interface has multiple levels. This is a common approach to creating a more flexible and organized structure in exported data.

Here are some steps you can consider to implement this:

Define Node Prefixes: Determine a consistent naming convention for node prefixes based on the levels in your hierarchical structure. This prefix will help identify the hierarchy of each record in the CSV file.
Update Interface Configuration: Modify the interface configuration in the SKYVVA integration application to include the new node prefixes. This involves updating mapping, specifying the levels, and configuring how child records are related to their parent records.
Adjust CSV File Generation Logic: Update the logic responsible for generating CSV files to incorporate the node prefixes. Ensure that each record is assigned the appropriate prefix based on its position in the hierarchy.

[su_box title="Note" box_color="#f70055" title_color="#000000"]The generated CSV file supports V3 hierarchy and has been Implemented for adapter Google Drive, DropBox, One Drive, Google Pub/Sub, and Amazon S3.[/su_box]

Business Scenario, we need to generate the hierarchical CSV like this: NodeAccount.FieldX,NodeContact.FieldX,NodeN.FieldX ValueOfAccount,ValueOfContact,ValueN

Required step:

Create an Integration
Create an Outbound Adapter e.g., Google Drive

Create an Outbound Interface -> set Interface API Version: V3 -> Do Mapping -> link Adapter with interface

Go to Interface Detail -> Scroll down to SOQL Query for filter sObject -> Set the condition on the file Filter Query

Click on the Manual Process button to callout the records

After clicking Send, we got the Message Monitoring

Here is the Payload from Google Drive

Here is the generated CSV payload. You can see the generated CSV below. The mapping is hierarchical, generating nodes with dots as prefixes for field mapping inputs to the headers. For example, 'nodex.fieldx' represents the parent-child mapping.

[su_box title="Result:" box_color="#2a8af0" title_color="#000000"]When clicking the 'Manual Process' button to execute the callout, we receive the 'Message Success' along with the payload, which is determined based on the conditions set in the 'Filter Query' of the 'SOQL Query for filter sObject' section. As a result, Export Data V3 hierarchical in CSV File format is implemented for an internet adapter.[/su_box]