1.0 - Data Integration Validation - Vantage Customer Experience

Vantage Customer Experience User Guide

prodname
Vantage Customer Experience
vrm_release
1.0
category
User Guide
featnum
B035-3800-099K
The tables that you use when you create an API data integration must be valid. This section includes the schema for each table type. See API Request and Response Tables.

Inbound Response and Outbound Source Table

Each row in the table represents the data sent or received in each individual API call.

CREATE MULTISET TABLE ${databaseName}.${tableName} (
    Execution_Id VARCHAR(12) CHARACTER SET LATIN CASESPECIFIC,
    Integration_Id VARCHAR(12) CHARACTER SET LATIN CASESPECIFIC,
    Object_Id VARCHAR(40) CHARACTER SET UNICODE,
    Object_Order INTEGER NOT NULL,
    Path VARCHAR(32000) NOT NULL CHARACTER SET UNICODE,
    Element_Property VARCHAR(32000) NOT NULL CHARACTER SET UNICODE,
    Element_Property_Value VARCHAR(32000) CHARACTER SET UNICODE,
    Element_Property_Datatype VARCHAR(50) CHARACTER SET LATIN,
    Element_Order INTEGER NOT NULL)
PRIMARY INDEX (Execution_Id);

Outbound Response

CREATE MULTISET TABLE ${databaseName}.${tableName} (
        Execution_Id VARCHAR(12) CHARACTER SET LATIN CASESPECIFIC,
        Integration_Id VARCHAR(12) CHARACTER SET LATIN CASESPECIFIC,
        Object_Id VARCHAR(40),
        Object_Order INTEGER,
        Path VARCHAR(32000),
        Element_Property VARCHAR(32000),
        Element_Property_Value VARCHAR(32000),
        Element_Property_Datatype VARCHAR(50) CHARACTER SET LATIN,
        Element_Order INTEGER,
        Request_Object_Order INTEGER,
        Request_Object_Id VARCHAR(40),
        Response_Status INTEGER NOT NULL,
        Response_Content_Type VARCHAR(128) CHARACTER SET LATIN,
        Response_Body VARCHAR(32000)
) PRIMARY INDEX (Object_Id);