1. How to Export CSV Hierarchical Payload?

Internet Adapter can execute a callout with a CSV payload for the V3 hierarchy that has Multiple Levels

Objectives of the Enhancement:

1. Enhanced Flexibility: The primary goal is to make the export functionality more adaptable, especially when dealing with multi-level hierarchical data in CSV format.
2. Child Record Generation: The enhancement intends to streamline the generation of child records within this hierarchical structure.

Expected Outcome:

• Hierarchical Structure Clarification: The introduction of node prefixes should bring clarity to the hierarchy, making it easier to detect different levels of data within the CSV file.
• Improved Data Organization: The node prefixes should facilitate better organization, especially when there are multiple levels of data, making it easier to interpret relationships between parent and child records.
• Enhanced Flexibility: The adaptation should ensure that the CSV export feature becomes more flexible, accommodating various levels of hierarchy efficiently.

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]

• The ‘Manual Process’ button triggers the execution of a callout, leading to a ‘Message Success’ response in the SKYVVA integration app. This success message is maintained by a payload generated through conditions specified in the ‘Filter Query’ of the ‘SOQL Query for filter sObject’ section. This ensures that the exported data in the CSV File format adheres to predefined criteria.
• The Export Data V3 hierarchical in CSV File format specifically caters to the internet adapter functionality within the SKYVVA integration app. By leveraging the ‘Filter Query,’ users can customize the data exported based on their specific requirements. The hierarchical structure ensures that the exported data maintains a well-organized format, crucial for handling complex datasets.
• This up-to-date process allows users to manually initiate data export, ensuring flexibility and control. The successful execution of the callout, coupled with the attachment to filter conditions, guarantees that the exported data aligns with the desired parameters. The CSV File format further facilitates easy data manipulation and analysis, making the SKYVVA integration app a robust solution for internet adapter business scenarios.

[su_box title=”Note” box_color=”#FF3046″ 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]

Generating Flat CSV Payload with Execute Callout V3

Key Points:

1. Level Mapping: The initial step involves mapping a level within the system, likely associating fields or attributes to the target side.
2. Callout V3 Execution: This execution seems to trigger a process or function (Callout V3) responsible for generating field maps based on the mapped level.
3. No Prefix Generation: The distinct expectation here is that the output of this process should only generate field maps without any prefixes attached.

Expected Outcome:

• Field Map Generation: The main outcome anticipated from the execution of Callout V3 after level mapping is the creation of field maps. These maps likely define the relationship between data elements and their destination or usage.
• Absence of Prefixes: There’s an explicit expectation that these field maps will not contain any prefixes. This suggests a desire for a clean and direct mapping output without additional identifiers or naming conventions.

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

[su_box title=”Result:” box_color=”#2a8af0″ title_color=”#000000″]After execution, the generated CSV payload does not have any prefixes when you have mapped a level in the mapping.[/su_box]

• If the user mapped a level in the mapping, it’s essential to ensure that the generated CSV payload includes the necessary prefixes after execution in the SKYVVA integration app. The absence of prefixes might be due to mapping configurations or data transformation issues.
• Firstly, review the mapping settings to confirm that the user correctly defined the mappings for the desired level. Check for any missing prefixes or naming conventions in the mapping configuration that might impact the CSV output.
• Additionally, inspect the data transformation logic within the mapping. Verify that the transformation rules are correctly applying the prefixes during the execution process. Look out for any conditional statements or expressions that might affect the prefix generation and adjust them accordingly.
• If the issue persists, consider checking the integration settings and the source data format to guarantee compatibility with the mapping specifications. It’s crucial to align the mapping structure with the source data to ensure accurate prefix application in the generated CSV payload.