This request method allows you to update Data Sources on the platform.

Enables scenarios where data sets maintained in other systems (e.g. SAP, Salesforce) can be updated into apps automatically.

Updates to a Data Source will be automatically synchronized to mobile devices by the platform.  Thus if a Data Source is used in a Form or other Screen type, that Data Source can be kept continuously up to date via this API.

Currently, Data Sources cannot be deleted nor can they be created by this API – this is to protect existing Screens that use these Data Sources.  

Thus, the Data Source must already exist on our platform and be referenced by its unique ExternalId for an API update to succeed.

Data Sources have a maximum limit of 50,000 rows.  If more rows are required please contact our support team.

On the Cloud, this API is available via SSL-secured HTTPS connection using the REST PUT verb.
The format query string parameter controls the desired response format.  Specify either XML or JSON.

/api/v2/datasource?format=xml/json

You may use either JSON or XML formats in your PUT request.
You indicate this by setting the ContentType HTTP header as "application/json" or "application/xml". If no ContentType is specified, XML format is assumed.

All XML formatted requests must specify the following XML namespace in the data source root element:
xmlns:i="http://www.w3.org/2001/XMLSchema-instance"

ADDITIONAL INFO

• API Explorer
• General Info & Status Codes

CONTENTS

• Endpoints & API Explorer
• Parameters
• Example

Endpoints & API Explorer

Parameters

The required parameters for a PUT request to the Data Sources API are outlined below.

DataSource (<DataSource>)

Header (<Header>)

Row (<Row>)

Each Row is a collection of Val (<Val>) items, which are the individual column values for that Row. 

Every Row must contain at least two Vals and must have as many Vals as there are Headers (columns).

The first Val should be the unique identifier or key that will be used as the answer value should this Data Source row be selected in a Form. The first Val is also critical as the key for performing incremental deletes through the DeletedRows field mentioned above.

The second Val should be the default displayable label text of the row.  You can override this default by configuring the Display Options field in the Data Source "Settings" page of the secure website.

Example

Given that the API is REST-based, you can access the API directly via your web browser to test it using a REST plugin like the Postman plugin for Google Chrome.

PUT Request – XML  

PUT https://secure.appenate.com/api/v2/DataSource?format=xml 
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>
<DataSource>
<CompanyId>1</CompanyId>
<IntegrationKey>xxxxxxxxxxxxxxx</IntegrationKey>
<Name>Favorite Sports</Name>
<ExternalId>SPORTS-001</ExternalId>
<Rows>
<Row>
<Val>AH</Val>
<Val>Air Hockey</Val>
<Val>This is some additional information about Air Hockey</Val>
<Val>http://mywebsite.com/images/air-hockey.jpg</Val>
</Row>
<Row>
<Val>FB</Val>
<Val>Football</Val>
<Val>This is some additional information about Football</Val>
<Val>http://mywebsite.com/images/football.jpg</Val>
</Row>
<Row>
<Val>CH</Val>
<Val>Chess (We have no additional info or images for this sport)</Val>
<Val />
<Val />
</Row>
</Rows>
</DataSource>

PUT Response – XML (Error example) 

HTTP/1.1 400 Bad Request
Content-Type: application/xml

<?xml version="1.0" encoding="UTF-8"?>
<DataSourceResponse>
<ResponseStatus>
<ErrorCode>ArgumentException</ErrorCode>
<Errors />
<Message>Missing parameters</Message>
</ResponseStatus>
</DataSourceResponse>