Overview

Skill Level: Intermediate

Prerequisites

This interface is used for programmatically creating or updating a Relational Table in Watson Campaign Automation.

This operation requires a mapping file and source file that is stored on the FTP server that is related to the Watson Campaign Automation account used to login. When the Relational Table source and mapping files are uploaded to the FTP server, you can make an ImportTable API call to start the job. See Relational Table Definition and Column Mapping Format for more information.

Note:¬†This operation does not associate the relational table to a database. See “Associate Relational Data to Contacts in a Database” for creating the association.

The table information shows the syntax for the API request and response.

Step-by-step

  1. Syntax of the request and response XML for ImportTable

    Operation <ImportTable>
    Elements MAP_FILE The name of the Mapping file in the upload directory on the FTP server to use for the import.  
      SOURCE_FILE The name of the file that contains the Relational Table data to use in the import. This file must be in the upload directory on the FTP server.  
      EMAIL Optional If specified, this email address receives notification when the job is complete.
      FILE_ENCODING Optional

    Defines the encoding of the source file. Supported values are:

    • UTF-8
    • ISO-8859-1

    If not specified, the Watson Campaign Automation uses the Org default encoding.

    Example
    <Envelope>
      <Body>
        <ImportTable>
          <MAP_FILE>table_import_map.xml</MAP_FILE>
          <SOURCE_FILE>table_create.csv</SOURCE_FILE>
        </ImportTable>
      </Body>
    </Envelope>
    
    Response <RESULT>
    Elements SUCCESS True if successful.  
      JOB_ID Identifies the Acoustic Campaign background job that is created and scheduled for this import.  
    Example
    <Envelope>
      <Body>
        <RESULT>
          <SUCCESS>TRUE</SUCCESS>
          <JOB_ID>108518</JOB_ID>
        </RESULT>
      </Body>
    </Envelope>
    

Join The Discussion

Your email address will not be published. Required fields are marked *