CData Cloud offers access to Act-On across several standard services and protocols, in a cloud-hosted solution. Any application that can connect to a MySQL or SQL Server database can connect to Act-On through CData Cloud.
CData Cloud allows you to standardize and configure connections to Act-On as though it were any other OData endpoint, or standard SQL Server/MySQL database.
This page provides a guide to Establishing a Connection to Act-On in CData Cloud, as well as information on the available resources, and a reference to the available connection properties.
Establishing a Connection shows how to authenticate to Act-On and configure any necessary connection properties to create a database in CData Cloud
Accessing data from Act-On through the available standard services and CData Cloud administration is documented in further details in the CData Cloud Documentation.
Connect to Act-On by selecting the corresponding icon in the Database tab. Required properties are listed under Settings. The Advanced tab lists connection properties that are not typically required.
Act-On uses the OAuth authentication standard. To authenticate using OAuth, you will need to create an app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties.
For authentication, the only difference between the two methods is that you must set two additional connection properties when using custom OAuth applications.
After setting the following connection properties, you are ready to connect:
When you connect, the Cloud opens the OAuth endpoint in your default browser. Log in and grant permissions to the application. The Cloud then completes the OAuth process as follows:
First, get an OAuthAccessToken by setting the following connection properties:
Then call stored procedures to complete the OAuth exchange:
After you have obtained the access and refresh tokens, you can connect to data and refresh the OAuth access token either automatically or manually.
Automatic Refresh of the OAuth Access Token
To have the driver automatically refresh the OAuth access token, set the following on the first data connection:
Manual Refresh of the OAuth Access Token
The only value needed to manually refresh the OAuth access token when connecting to data is the OAuth refresh token.
Use the RefreshOAuthAccessToken stored procedure to manually refresh the OAuthAccessToken after the ExpiresIn parameter value returned by GetOAuthAccessToken has elapsed, then set the following connection properties:
Then call RefreshOAuthAccessToken with OAuthRefreshToken set to the OAuth refresh token returned by GetOAuthAccessToken. After the new tokens have been retrieved, open a new connection by setting the OAuthAccessToken property to the value returned by RefreshOAuthAccessToken.
Finally, store the OAuth refresh token so that you can use it to manually refresh the OAuth access token after it has expired.
Option 1: Obtain and Exchange a Verifier Code
To obtain a verifier code, you must authenticate at the OAuth authorization URL.
Follow the steps below to authenticate from the machine with an internet browser and obtain the OAuthVerifier connection property.
On the headless machine, set the following connection properties to obtain the OAuth authentication values.
After the OAuth settings file is generated, you need to re-set the following properties to connect:
Option 2: Transfer OAuth Settings
Prior to connecting on a headless machine, you need to install and create a connection with the driver on a device that supports an internet browser. Set the connection properties as described in "Desktop Applications" above.
After completing the instructions in "Desktop Applications", the resulting authentication values are encrypted and written to the location specified by OAuthSettingsLocation. The default filename is OAuthSettings.txt.
After you have successfully tested the connection, copy the OAuth settings file to your headless machine.
On the headless machine, set the following connection properties to connect to data:
You may choose to create your own OAuth Application Credentials when you want to
Follow the steps below to create a custom OAuth app and obtain the connection properties in a specific OAuth authentication flow.
Sign up to https://developer.act-on.com/provision/. After registering your account on Act-On you will get an email with the following connection properties:
By default, the Cloud attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store.
To specify another certificate, see the SSLServerCert property for the available formats to do so.
To connect through the Windows system proxy, you do not need to set any additional connection properties. To connect to other proxies, set ProxyAutoDetect to false.
In addition, to authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.
Set the following properties:
The CData Cloud models entities in the Act-On API as tables, views, and stored procedures. These are defined in schema files, which are simple, text-based configuration files.
Lists in Act-On are exposed as views with the convention List_ListName. For each list there is another view List_ListName_Score where you can see the score
of the people in the list.
Same logic for Segments in Act-On, they are exposed as views as Segment_SegmentName. And have an equivalent view Segment_SegmentName_Score.
Any changes you make to your Act-On account, such as adding a new list, adding new columns, or changing the data type of a column, will immediately be reflected
when you connect using the driver.
The Cloud offloads as much of the SELECT statement processing as possible to the Act-On APIs and then processes the rest of the query within the Cloud. The following sections document API limitations and requirements.
Views are tables that cannot be modified. Typically, read-only data are shown as views.
Stored Procedures are function-like interfaces to the data source. They can be used to search, update, and modify information in the data source.
The Cloud models the data in Act-On as a list of tables in a relational database that can be queried using standard SQL statements.
Name | Description |
List_MyList | Create, update, delete, and query records of a List. |
Optout | Upsert, delete and query records of a Optout list. |
Create, update, delete, and query records of a List.
Every list that is created in your Act-On account is represented by a new table that is dynamically retrieved from your Act-On account. The name of the table has the following format:
List_nameOfTheList
For example, if the list in the Act-On UI is called 'MyList', the name of the table in the driver would be 'List_MyList'.
This is an example on how a list is exposed as table.
Query records of the specified table.:
SELECT * FROM [List_MyList]
Create a new record in the table.
Note: The ListId is required to insert a new record into a table.
All the fields that are not read-only can be specified.
INSERT INTO [List_MyList] ([First Name], [Last Name], [E-mail Address], [ListId]) VALUES ('John', 'Doe', '[email protected]', 'l-000d')
Update details of a specific record.
Note: To update a record from a table, the ListId and E-mail Address must be specified.
All the fields that are not read-only can be specified.
UPDATE [List_MyList] SET [First Name] = 'Mohit', [Last Name] = 'Chaturvedi', [E-mail Address] = '[email protected]' WHERE [ListId] = 'l-000d' AND [E-mail Address] = '[email protected]'
Update details of a specific record if it exists, else will insert a new record.
Note: To upsert a record from a table, the ListId and E-mail Address must be specified.
All the fields that are not read-only can be specified.
UPSERT INTO [List_MyList] ([First Name], [Last Name], [E-mail Address], [ListId]) VALUES ('Shubham', 'Prakash', '[email protected]', 'l-000a')
Delete a record of a table.
Note: To Delete a record the ListId and _contact_id_ must be specified.
All the fields that are not read-only can be specified.
DELETE FROM List_MyList WHERE [ListId] = 'l-000d' AND [_contact_id_] = 'l-000d:10'
Name | Type | ReadOnly | Description |
_contact_id_ [KEY] | String | False |
The _contact_id_ of the List_MyList. |
First Name | String | False |
The First Name of the List_MyList. |
Last Name | String | False |
The Last Name of the List_MyList. |
E-mail Address | String | False |
The E-mail Address of the List_MyList. |
_FORM | String | False |
The _FORM of the List_MyList. |
_CAMPAIGN | String | False |
The _CAMPAIGN of the List_MyList. |
_IPADDR | String | False |
The _IPADDR of the List_MyList. |
_BROWSER | String | False |
The _BROWSER of the List_MyList. |
_JSTZO | String | False |
The _JSTZO of the List_MyList. |
_TIME | String | False |
The _TIME of the List_MyList. |
_REFERRER | String | False |
The _REFERRER of the List_MyList. |
_EMAIL_REFERRER | String | False |
The _EMAIL_REFERRER of the List_MyList. |
_FORM_URL | String | False |
The _FORM_URL of the List_MyList. |
_SEARCH | String | False |
The _SEARCH of the List_MyList. |
_GEO_NAME | String | False |
The _GEO_NAME of the List_MyList. |
_GEO_COUNTRY_CODE | String | False |
The _GEO_COUNTRY_CODE of the List_MyList. |
_GEO_COUNTRY | String | False |
The _GEO_COUNTRY of the List_MyList. |
_GEO_STATE | String | False |
The _GEO_STATE of the List_MyList. |
_GEO_CITY | String | False |
The _GEO_CITY of the List_MyList. |
_GEO_POSTAL_CODE | String | False |
The _GEO_POSTAL_CODE of the List_MyList. |
__created_date | Datetime | False |
The __created_date of the List_MyList. |
__modified_date | Datetime | False |
The __modified_date of the List_MyList. |
ListId | String | False |
The ListId of the List_MyList. |
Upsert, delete and query records of a Optout list.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example:
SELECT * FROM Optout WHERE Timestamp >= '2022-09-15 08:53:50.111' AND Timestamp <= '2022-09-16 00:30:33.14' SELECT * FROM Optout WHERE Timestamp > '2022-09-15 08:53:50.111' AND Timestamp < '2022-09-16 00:30:33.14'
Upsert can be executed by specifying the Email column. Following is an example of how to insert a single email into this table
UPSERT INTO Optout(Email) VALUES ('[email protected]')
Multiple emails can also be added or updated. Following is an example of how to insert multiple emails into this table
UPSERT INTO Optout(Email) VALUES ('[email protected];[email protected]')
Delete can be executed by specifying the Email column in the WHERE Clause. Following is an example of how to delete a single email from this table
DELETE FROM Optout WHERE Email = '[email protected]'
Multiple emails can also be deleted. Following is an example of how to delete multiple emails into this table
DELETE FROM Optout WHERE Email = '[email protected];[email protected]'
Name | Type | ReadOnly | Description |
String | False |
Email of the user. | |
Origin | String | True |
Origin. |
Timestamp | Timestamp | True |
When the user joined the list. |
Views are similar to tables in the way that data is represented; however, views are read-only.
Queries can be executed against a view as if it were a normal table.
Name | Description |
Campaigns | Query the available campaigns ActOn. |
Categories | Query the available categories of subscription in ActOn. |
DrilldownReports | Query detailed reports about messages in ActOn. |
Hardbounce | Query records of a Hardbounce list. |
Images | Query the available images on your ActOn account. |
Media | Query the available media on your ActOn account. |
Messages | Query the available messages in ActOn. |
OtherLists | Query the hardbounce, spam complaint and optout lists on ActOn. This view has been deprecated. |
Programs | Query the available programs on ActOn. |
Reports | Query the available reports in ActOn. |
ReportsByPeriod | Query the reports related to messages in ActOn. |
ScoreDetails | Query the score details of a contact. |
Spamcomplaint | Query records of a Spamcomplaint list. |
SubscriptionOptOuts | Query the available subscriptions in ActOn. |
Users | Query the email senders for the current account in ActOn. |
Query the available campaigns ActOn.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Campaigns WHERE Id = 0001 SELECT * FROM Campaigns WHERE Id IN (0001, 0002)
Name | Type | Description |
Id [KEY] | String | The Id of the campaign. |
Name | String | The name of the campaign. |
Created | Datetime | When the campaign was created. |
AssetIds | String | Asset ids of the campaigns. |
Description | String | Description of the campaign. |
Modified | Datetime | When the campaign was last modified. |
Urls | String | Urls related to the campaign. |
Query the available categories of subscription in ActOn.
Name | Type | Description |
Id [KEY] | String | The Id of the category. |
Name | String | The name of the category. |
Description | String | Description of the category. |
HeaderId | String | Header id. |
HeaderName | String | Header name. |
Query detailed reports about messages in ActOn.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
MessageId and Drilldown are required to select from this view and will be filtered by the Act-On API.
SELECT * FROM DrilldownReports WHERE MessageId = 's-0003-1803' AND Drilldown = 'SENT'
Name | Type | Description |
MessageId | String | The id of the message. |
Drilldown | String | Type of message.
The allowed values are SENT, SUPPRESSED, OPENED, CLICKED, BOUNCED, OPT_OUT, SPAM. |
String | The receiver email. | |
Name | String | Name of the receiver. |
ListId | String | Id of the list the receiver belongs to. |
RecId | String | The id of the receiver. |
Timestamp | Datetime | When the message was sent. |
Query records of a Hardbounce list.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example:
SELECT * FROM Hardbounce WHERE Timestamp >= '2022-09-15 08:53:50.111' AND Timestamp <= '2022-09-16 00:30:33.14' SELECT * FROM Hardbounce WHERE Timestamp > '2022-09-15 08:53:50.111' AND Timestamp < '2022-09-16 00:30:33.14'
Name | Type | Description |
String | Email of the user. | |
Origin | String | Origin. |
Timestamp | Timestamp | When the user joined the list. |
Query the available images on your ActOn account.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Images WHERE FolderName = 'New Folder' SELECT Name, FolderName FROM Images WHERE FolderName IN ('New Folder', 'Default Folder')
Name | Type | Description |
Id [KEY] | String | Id of the image. |
FolderName | String | Name of the folder that contains the image. |
Name | String | Name of the image. |
CreationTime | Datetime | When the image was created. |
LastModified | Datetime | When the image was last modified. |
ImageUrl | String | Link to the image. |
ThumbUrl | String | Link to the image. |
Size | Int | Size of the image. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
Type | String | Identifier for the next page of results. Do not set this value manually. |
Query the available media on your ActOn account.
Act-On does not support any column for filtering this view.
Name | Type | Description |
Id [KEY] | String | Id of the image. |
FolderName | String | Name of the folder that contains the image. |
Name | String | Name of the image. |
CreationTime | Datetime | When the image was created. |
LastModified | Datetime | When the image was last modified. |
Url | String | Link to the media. |
Size | Int | Size of the image. |
Query the available messages in ActOn.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
SELECT * FROM Messages WHERE Type = 'SENT'Type can be one of: SENT, DRAFT, TEMPLATE, TRIGGERED, FAILED, SCHEDULED
Name | Type | Description |
Id [KEY] | String | The Id of the message. |
Timestamp | Datetime | When the message has been sent. |
Title | String | Title of the message. |
FolderName | String | The folder where the message is contained. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
Type | String | Used as a filter to retrieve different types of messages.
The allowed values are SENT, DRAFT, TEMPLATE, TRIGGERED, FAILED, SCHEDULED. |
Query the hardbounce, spam complaint and optout lists on ActOn. This view has been deprecated.
To query data from this view, you must specify Type.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM [OtherLists] WHERE Type = 'OPTOUT' SELECT * FROM [OtherLists] WHERE Type = 'OPTOUT' AND CreatedAfter = '2018-08-28T14:37:48.923+02:00' AND CreatedBefore = '2018-08-28T14:37:48.925+02:00' SELECT * FROM [OtherLists] WHERE Type = 'HARDBOUNCE' AND CreatedBefore = '2019-09-28T14:39:48.924+02:00'
Name | Type | Description |
String | Email of the user. | |
Timestamp | Datetime | When the user joined the list. |
Origin | String | |
Type | String | The type of list.
The allowed values are HARDBOUNCE, SPAMCOMPLAINT, OPTOUT. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
CreatedBefore | String | Only records created before the supplied value will be returned. |
CreatedAfter | String | Only records created after the supplied value will be returned. |
Query the available programs on ActOn.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Programs WHERE Type = 'RACK'
Name | Type | Description |
Id [KEY] | String | The id of the program. |
Name | String | The name of the program. |
IsFavorite | Bool | Flag denoting if the program is among the 'favorite' ones. |
Description | String | The description of the program. |
SrcIds | String | Ids of the lists involved in the program. |
SrcNames | String | Name of the lists involved in the program. |
MessageIds | String | Ids of the messages sent within the program. |
Created | Datetime | When the program was created. |
Modified | Datetime | When the program was last modified. |
NextRun | Datetime | When the program is going to run again. |
State | String | The state of the program. |
Running | Bool | Flag denoting if the program is running or not. |
Active | Int | Flag denoting if the program is active or not. |
Scheduled | Bool | Flag denoting if the program is scheduled or not. |
TagNames | String | List of tags related to the program. |
Valid | Bool | Flag denoting if the program is valid or not. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description |
Type | String | Type of the program, used for filtering.
The allowed values are RACK, EVENT, LIST_MAINT. |
Query the available reports in ActOn.
To query data from this view, you must specify MessageId.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Reports WHERE MessageId = 'd-0008' SELECT * FROM Reports WHERE MessageId IN ('d-0008', 's-0004-1809')
Name | Type | Description |
MessageId [KEY] | String | The Id of the message. |
Title | String | The title of the message. |
Status | String | The status of the message. |
Bounced | Int | The number of times the message generated a bounce. |
Clicked | String | The number of times the message has been clicked. |
Delivered | Int | The number of times the message has been delivered. |
EffectiveOpened | String | . |
HardBounced | Int | The number of times the message generated hard bounce. |
LastClick | Datetime | The timestamp of the last click. |
LastOpen | Datetime | The timestamp of the last opening. |
NotOpened | Int | The number of times the message has not been opened. |
NotSent | String | The number of times the message has not been sent. |
Opened | String | The number of times the message was opened. |
OptOut | Int | The number of times the receiver opted out. |
RedbroadcastClick | Int | . |
Sent | Int | The number of times the message has been sent. |
SentTo | String | The ids of the people who received the email. |
SoftBounced | Int | The number of times the message generated soft bounce. |
Spam | Int | The number of times has been considered as spam. |
Subject | String | The subject of the message. |
SuppressedOn | String | . |
Query the reports related to messages in ActOn.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM ReportsByPeriod WHERE Period = 'January 2018' SELECT * FROM ReportsByPeriod WHERE Period IN ('January 2018', 'March 2018')If not specified, the period will be the current month.
Name | Type | Description |
Period | String | The period defined in the format '{month} yyyy' used to filter the reports. If not specified, report for the current month will return. |
DayOfMonth | Int | The day of the month the report is about. |
DayOfWeek | Int | The day of the week the report is about. |
Sent | Int | The number of sent messages. |
Bounced | Int | The number of bounced messages. |
Clicked | Int | The number of clicked messages. |
Opened | Int | The number of opened messages. |
OptedOut | Int | Th number of opted out. |
Query the score details of a contact.
To query data from this view, you must specify ContactId.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM ScoreDetails WHERE ContactId = 'l-0004:2' SELECT * FROM ScoreDetails WHERE ContactId IN ('l-0004:2', 'l-0004:3')
Name | Type | Description |
ContactId [KEY] | String | Unique identifier of the contact. |
ActivityId | String | Unique identifier of the activity. |
Action | String | Brief description of the action. |
IdType | String | Type of the activity. |
Profile | Boolean | Whether or not the user has a profile. |
Score | Integer | Score of the activity. |
Specific | Boolean | Whether or not the activity is specific. |
Ago | Integer | Days ago that activity happened. |
InScoreRange | Boolean | Whether or not the activity is in score range. |
What | String | Object of the activity. |
When | Datetime | When the activity happened. |
Bin | String | Subject of the activity. |
Verb | String | Description of the activity. |
Query records of a Spamcomplaint list.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
For example:
SELECT * FROM Spamcomplaint WHERE Timestamp >= '2022-09-15 08:53:50.111' AND Timestamp <= '2022-09-16 00:30:33.14' SELECT * FROM Spamcomplaint WHERE Timestamp > '2022-09-15 08:53:50.111' AND Timestamp < '2022-09-16 00:30:33.14'
Name | Type | Description |
String | Email of the user. | |
Origin | String | Origin. |
Timestamp | Timestamp | When the user joined the list. |
Query the available subscriptions in ActOn.
The Cloud will use the Act-On API to process WHERE clause conditions built with the following columns and operators. The rest of the filter is executed client side within the Cloud.
Category is required to select from this view.
For example, the following query is processed server side:
SELECT * FROM SubscriptionOptOuts WHERE Category = 'test'
Name | Type | Description |
String | The email of the subscribed user. | |
Timestamp | Datetime | The time when the user subscribed. |
Category | String | The category of the subscription. This attribute is required for select operations. |
Query the email senders for the current account in ActOn.
Act-On does not support any column for filtering this view.
Name | Type | Description |
UserId [KEY] | String | The universally unique identifier of the user. |
String | The email of the user. | |
Name | String | The name of the user. |
Title | String | The title of the user. |
Cell | String | The mobile phone of the user. |
Phone | String | The phone number of the user. |
Fax | String | The fax of the user. |
isVerified | Bool | Flag denoting if the user has been verified or not. |
Stored procedures are function-like interfaces that extend the functionality of the Cloud beyond simple SELECT/INSERT/UPDATE/DELETE operations with Act-On.
Stored procedures accept a list of parameters, perform their intended function, and then return any relevant response data from Act-On, along with an indication of whether the procedure succeeded or failed.
Name | Description |
You can query the system tables described in this section to access schema information, information on data source functionality, and batch operation statistics.
The following tables return database metadata for Act-On:
The following tables return information about how to connect to and query the data source:
The following table returns query statistics for data modification queries:
Lists the available databases.
The following query retrieves all databases determined by the connection string:
SELECT * FROM sys_catalogs
Name | Type | Description |
CatalogName | String | The database name. |
Lists the available schemas.
The following query retrieves all available schemas:
SELECT * FROM sys_schemas
Name | Type | Description |
CatalogName | String | The database name. |
SchemaName | String | The schema name. |
Lists the available tables.
The following query retrieves the available tables and views:
SELECT * FROM sys_tables
Name | Type | Description |
CatalogName | String | The database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view. |
TableType | String | The table type (table or view). |
Description | String | A description of the table or view. |
IsUpdateable | Boolean | Whether the table can be updated. |
Describes the columns of the available tables and views.
The following query returns the columns and data types for the Images table:
SELECT ColumnName, DataTypeName FROM sys_tablecolumns WHERE TableName='Images'
Name | Type | Description |
CatalogName | String | The name of the database containing the table or view. |
SchemaName | String | The schema containing the table or view. |
TableName | String | The name of the table or view containing the column. |
ColumnName | String | The column name. |
DataTypeName | String | The data type name. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The storage size of the column. |
DisplaySize | Int32 | The designated column's normal maximum width in characters. |
NumericPrecision | Int32 | The maximum number of digits in numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The column scale or number of digits to the right of the decimal point. |
IsNullable | Boolean | Whether the column can contain null. |
Description | String | A brief description of the column. |
Ordinal | Int32 | The sequence number of the column. |
IsAutoIncrement | String | Whether the column value is assigned in fixed increments. |
IsGeneratedColumn | String | Whether the column is generated. |
IsHidden | Boolean | Whether the column is hidden. |
IsArray | Boolean | Whether the column is an array. |
IsReadOnly | Boolean | Whether the column is read-only. |
IsKey | Boolean | Indicates whether a field returned from sys_tablecolumns is the primary key of the table. |
Lists the available stored procedures.
The following query retrieves the available stored procedures:
SELECT * FROM sys_procedures
Name | Type | Description |
CatalogName | String | The database containing the stored procedure. |
SchemaName | String | The schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure. |
Description | String | A description of the stored procedure. |
ProcedureType | String | The type of the procedure, such as PROCEDURE or FUNCTION. |
Describes stored procedure parameters.
The following query returns information about all of the input parameters for the RefreshOAuthAccessToken stored procedure:
SELECT * FROM sys_procedureparameters WHERE ProcedureName='RefreshOAuthAccessToken' AND Direction=1 OR Direction=2
Name | Type | Description |
CatalogName | String | The name of the database containing the stored procedure. |
SchemaName | String | The name of the schema containing the stored procedure. |
ProcedureName | String | The name of the stored procedure containing the parameter. |
ColumnName | String | The name of the stored procedure parameter. |
Direction | Int32 | An integer corresponding to the type of the parameter: input (1), input/output (2), or output(4). input/output type parameters can be both input and output parameters. |
DataTypeName | String | The name of the data type. |
DataType | Int32 | An integer indicating the data type. This value is determined at run time based on the environment. |
Length | Int32 | The number of characters allowed for character data. The number of digits allowed for numeric data. |
NumericPrecision | Int32 | The maximum precision for numeric data. The column length in characters for character and date-time data. |
NumericScale | Int32 | The number of digits to the right of the decimal point in numeric data. |
IsNullable | Boolean | Whether the parameter can contain null. |
IsRequired | Boolean | Whether the parameter is required for execution of the procedure. |
IsArray | Boolean | Whether the parameter is an array. |
Description | String | The description of the parameter. |
Ordinal | Int32 | The index of the parameter. |
Describes the primary and foreign keys.
The following query retrieves the primary key for the Images table:
SELECT * FROM sys_keycolumns WHERE IsKey='True' AND TableName='Images'
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
IsKey | Boolean | Whether the column is a primary key in the table referenced in the TableName field. |
IsForeignKey | Boolean | Whether the column is a foreign key referenced in the TableName field. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
Describes the foreign keys.
The following query retrieves all foreign keys which refer to other tables:
SELECT * FROM sys_foreignkeys WHERE ForeignKeyType = 'FOREIGNKEY_TYPE_IMPORT'
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
PrimaryKeyName | String | The name of the primary key. |
ForeignKeyName | String | The name of the foreign key. |
ReferencedCatalogName | String | The database containing the primary key. |
ReferencedSchemaName | String | The schema containing the primary key. |
ReferencedTableName | String | The table containing the primary key. |
ReferencedColumnName | String | The column name of the primary key. |
ForeignKeyType | String | Designates whether the foreign key is an import (points to other tables) or export (referenced from other tables) key. |
Describes the primary keys.
The following query retrieves the primary keys from all tables and views:
SELECT * FROM sys_primarykeys
Name | Type | Description |
CatalogName | String | The name of the database containing the key. |
SchemaName | String | The name of the schema containing the key. |
TableName | String | The name of the table containing the key. |
ColumnName | String | The name of the key column. |
KeySeq | String | The sequence number of the primary key. |
KeyName | String | The name of the primary key. |
Describes the available indexes. By filtering on indexes, you can write more selective queries with faster query response times.
The following query retrieves all indexes that are not primary keys:
SELECT * FROM sys_indexes WHERE IsPrimary='false'
Name | Type | Description |
CatalogName | String | The name of the database containing the index. |
SchemaName | String | The name of the schema containing the index. |
TableName | String | The name of the table containing the index. |
IndexName | String | The index name. |
ColumnName | String | The name of the column associated with the index. |
IsUnique | Boolean | True if the index is unique. False otherwise. |
IsPrimary | Boolean | True if the index is a primary key. False otherwise. |
Type | Int16 | An integer value corresponding to the index type: statistic (0), clustered (1), hashed (2), or other (3). |
SortOrder | String | The sort order: A for ascending or D for descending. |
OrdinalPosition | Int16 | The sequence number of the column in the index. |
Returns information on the available connection properties and those set in the connection string.
When querying this table, the config connection string should be used:
jdbc:cdata:acton:config:
This connection string enables you to query this table without a valid connection.
The following query retrieves all connection properties that have been set in the connection string or set through a default value:
SELECT * FROM sys_connection_props WHERE Value <> ''
Name | Type | Description |
Name | String | The name of the connection property. |
ShortDescription | String | A brief description. |
Type | String | The data type of the connection property. |
Default | String | The default value if one is not explicitly set. |
Values | String | A comma-separated list of possible values. A validation error is thrown if another value is specified. |
Value | String | The value you set or a preconfigured default. |
Required | Boolean | Whether the property is required to connect. |
Category | String | The category of the connection property. |
IsSessionProperty | String | Whether the property is a session property, used to save information about the current connection. |
Sensitivity | String | The sensitivity level of the property. This informs whether the property is obfuscated in logging and authentication forms. |
PropertyName | String | A camel-cased truncated form of the connection property name. |
Ordinal | Int32 | The index of the parameter. |
CatOrdinal | Int32 | The index of the parameter category. |
Hierarchy | String | Shows dependent properties associated that need to be set alongside this one. |
Visible | Boolean | Informs whether the property is visible in the connection UI. |
ETC | String | Various miscellaneous information about the property. |
Describes the SELECT query processing that the Cloud can offload to the data source.
See SQL Compliance for SQL syntax details.
Below is an example data set of SQL capabilities. Some aspects of SELECT functionality are returned in a comma-separated list if supported; otherwise, the column contains NO.
Name | Description | Possible Values |
AGGREGATE_FUNCTIONS | Supported aggregation functions. | AVG, COUNT, MAX, MIN, SUM, DISTINCT |
COUNT | Whether COUNT function is supported. | YES, NO |
IDENTIFIER_QUOTE_OPEN_CHAR | The opening character used to escape an identifier. | [ |
IDENTIFIER_QUOTE_CLOSE_CHAR | The closing character used to escape an identifier. | ] |
SUPPORTED_OPERATORS | A list of supported SQL operators. | =, >, <, >=, <=, <>, !=, LIKE, NOT LIKE, IN, NOT IN, IS NULL, IS NOT NULL, AND, OR |
GROUP_BY | Whether GROUP BY is supported, and, if so, the degree of support. | NO, NO_RELATION, EQUALS_SELECT, SQL_GB_COLLATE |
OJ_CAPABILITIES | The supported varieties of outer joins supported. | NO, LEFT, RIGHT, FULL, INNER, NOT_ORDERED, ALL_COMPARISON_OPS |
OUTER_JOINS | Whether outer joins are supported. | YES, NO |
SUBQUERIES | Whether subqueries are supported, and, if so, the degree of support. | NO, COMPARISON, EXISTS, IN, CORRELATED_SUBQUERIES, QUANTIFIED |
STRING_FUNCTIONS | Supported string functions. | LENGTH, CHAR, LOCATE, REPLACE, SUBSTRING, RTRIM, LTRIM, RIGHT, LEFT, UCASE, SPACE, SOUNDEX, LCASE, CONCAT, ASCII, REPEAT, OCTET, BIT, POSITION, INSERT, TRIM, UPPER, REGEXP, LOWER, DIFFERENCE, CHARACTER, SUBSTR, STR, REVERSE, PLAN, UUIDTOSTR, TRANSLATE, TRAILING, TO, STUFF, STRTOUUID, STRING, SPLIT, SORTKEY, SIMILAR, REPLICATE, PATINDEX, LPAD, LEN, LEADING, KEY, INSTR, INSERTSTR, HTML, GRAPHICAL, CONVERT, COLLATION, CHARINDEX, BYTE |
NUMERIC_FUNCTIONS | Supported numeric functions. | ABS, ACOS, ASIN, ATAN, ATAN2, CEILING, COS, COT, EXP, FLOOR, LOG, MOD, SIGN, SIN, SQRT, TAN, PI, RAND, DEGREES, LOG10, POWER, RADIANS, ROUND, TRUNCATE |
TIMEDATE_FUNCTIONS | Supported date/time functions. | NOW, CURDATE, DAYOFMONTH, DAYOFWEEK, DAYOFYEAR, MONTH, QUARTER, WEEK, YEAR, CURTIME, HOUR, MINUTE, SECOND, TIMESTAMPADD, TIMESTAMPDIFF, DAYNAME, MONTHNAME, CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, EXTRACT |
REPLICATION_SKIP_TABLES | Indicates tables skipped during replication. | |
REPLICATION_TIMECHECK_COLUMNS | A string array containing a list of columns which will be used to check for (in the given order) to use as a modified column during replication. | |
IDENTIFIER_PATTERN | String value indicating what string is valid for an identifier. | |
SUPPORT_TRANSACTION | Indicates if the provider supports transactions such as commit and rollback. | YES, NO |
DIALECT | Indicates the SQL dialect to use. | |
KEY_PROPERTIES | Indicates the properties which identify the uniform database. | |
SUPPORTS_MULTIPLE_SCHEMAS | Indicates if multiple schemas may exist for the provider. | YES, NO |
SUPPORTS_MULTIPLE_CATALOGS | Indicates if multiple catalogs may exist for the provider. | YES, NO |
DATASYNCVERSION | The CData Data Sync version needed to access this driver. | Standard, Starter, Professional, Enterprise |
DATASYNCCATEGORY | The CData Data Sync category of this driver. | Source, Destination, Cloud Destination |
SUPPORTSENHANCEDSQL | Whether enhanced SQL functionality beyond what is offered by the API is supported. | TRUE, FALSE |
SUPPORTS_BATCH_OPERATIONS | Whether batch operations are supported. | YES, NO |
SQL_CAP | All supported SQL capabilities for this driver. | SELECT, INSERT, DELETE, UPDATE, TRANSACTIONS, ORDERBY, OAUTH, ASSIGNEDID, LIMIT, LIKE, BULKINSERT, COUNT, BULKDELETE, BULKUPDATE, GROUPBY, HAVING, AGGS, OFFSET, REPLICATE, COUNTDISTINCT, JOINS, DROP, CREATE, DISTINCT, INNERJOINS, SUBQUERIES, ALTER, MULTIPLESCHEMAS, GROUPBYNORELATION, OUTERJOINS, UNIONALL, UNION, UPSERT, GETDELETED, CROSSJOINS, GROUPBYCOLLATE, MULTIPLECATS, FULLOUTERJOIN, MERGE, JSONEXTRACT, BULKUPSERT, SUM, SUBQUERIESFULL, MIN, MAX, JOINSFULL, XMLEXTRACT, AVG, MULTISTATEMENTS, FOREIGNKEYS, CASE, LEFTJOINS, COMMAJOINS, WITH, LITERALS, RENAME, NESTEDTABLES, EXECUTE, BATCH, BASIC, INDEX |
PREFERRED_CACHE_OPTIONS | A string value specifies the preferred cacheOptions. | |
ENABLE_EF_ADVANCED_QUERY | Indicates if the driver directly supports advanced queries coming from Entity Framework. If not, queries will be handled client side. | YES, NO |
PSEUDO_COLUMNS | A string array indicating the available pseudo columns. | |
MERGE_ALWAYS | If the value is true, The Merge Mode is forcibly executed in Data Sync. | TRUE, FALSE |
REPLICATION_MIN_DATE_QUERY | A select query to return the replicate start datetime. | |
REPLICATION_MIN_FUNCTION | Allows a provider to specify the formula name to use for executing a server side min. | |
REPLICATION_START_DATE | Allows a provider to specify a replicate startdate. | |
REPLICATION_MAX_DATE_QUERY | A select query to return the replicate end datetime. | |
REPLICATION_MAX_FUNCTION | Allows a provider to specify the formula name to use for executing a server side max. | |
IGNORE_INTERVALS_ON_INITIAL_REPLICATE | A list of tables which will skip dividing the replicate into chunks on the initial replicate. | |
CHECKCACHE_USE_PARENTID | Indicates whether the CheckCache statement should be done against the parent key column. | TRUE, FALSE |
CREATE_SCHEMA_PROCEDURES | Indicates stored procedures that can be used for generating schema files. |
The following query retrieves the operators that can be used in the WHERE clause:
SELECT * FROM sys_sqlinfo WHERE Name = 'SUPPORTED_OPERATORS'
Note that individual tables may have different limitations or requirements on the WHERE clause; refer to the Data Model section for more information.
Name | Type | Description |
NAME | String | A component of SQL syntax, or a capability that can be processed on the server. |
VALUE | String | Detail on the supported SQL or SQL syntax. |
Returns information about attempted modifications.
The following query retrieves the Ids of the modified rows in a batch operation:
SELECT * FROM sys_identity
Name | Type | Description |
Id | String | The database-generated Id returned from a data modification operation. |
Batch | String | An identifier for the batch. 1 for a single operation. |
Operation | String | The result of the operation in the batch: INSERTED, UPDATED, or DELETED. |
Message | String | SUCCESS or an error message if the update in the batch failed. |
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider. Click the links for further details.
For more information on establishing a connection, see Establishing a Connection.
Property | Description |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
Property | Description |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
Property | Description |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
Property | Description |
MaxRows | Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses. |
Pagesize | The maximum number of results to return per page from Act-On. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
RowScanDepth | The maximum number of rows to scan to look for the columns available in a table. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
TypeDetectionScheme | Determines how to determine the data type of columns. |
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
Property | Description |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
The certificate to be accepted from the server when connecting using TLS/SSL.
string
""
If using a TLS/SSL connection, this property can be used to specify the TLS/SSL certificate to be accepted from the server. Any other certificate that is not trusted by the machine is rejected.
This property can take the following forms:
Description | Example |
A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
A path to a local file containing the certificate | C:\cert.cer |
The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
The MD5 Thumbprint (hex values can also be either space or colon separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
The SHA1 Thumbprint (hex values can also be either space or colon separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
If not specified, any certificate trusted by the machine is accepted.
Use '*' to signify to accept all certificates. Note that this is not recommended due to security concerns.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
Property | Description |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
The verbosity level that determines the amount of detail included in the log file.
string
"1"
The verbosity level determines the amount of detail that the Cloud reports to the Logfile. Verbosity levels from 1 to 5 are supported. These are detailed in the Logging page.
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
Property | Description |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
string
""
Listing the schemas from databases can be expensive. Providing a list of schemas in the connection string improves the performance.
This section provides a complete list of the Miscellaneous properties you can configure in the connection string for this provider.
Property | Description |
MaxRows | Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses. |
Pagesize | The maximum number of results to return per page from Act-On. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
RowScanDepth | The maximum number of rows to scan to look for the columns available in a table. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
TypeDetectionScheme | Determines how to determine the data type of columns. |
Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
int
-1
Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
The maximum number of results to return per page from Act-On.
int
1000
The Pagesize property affects the maximum number of results to return per page from Act-On. Setting a higher value may result in better performance at the cost of additional memory allocated per page consumed.
This property indicates whether or not to include pseudo columns as columns to the table.
string
""
This setting is particularly helpful in Entity Framework, which does not allow you to set a value for a pseudo column unless it is a table column. The value of this connection setting is of the format "Table1=Column1, Table1=Column2, Table2=Column3". You can use the "*" character to include all tables and all columns; for example, "*=*".
The maximum number of rows to scan to look for the columns available in a table.
int
50
The columns in a table must be determined by scanning table rows. This value determines the maximum number of rows that will be scanned.
Setting a high value may decrease performance. Setting a low value may prevent the data type from being determined properly, especially when there is null data.
The value in seconds until the timeout error is thrown, canceling the operation.
int
60
If Timeout = 0, operations do not time out. The operations run until they complete successfully or until they encounter an error condition.
If Timeout expires and the operation is not yet complete, the Cloud throws an exception.
Determines how to determine the data type of columns.
string
"RowScan"
None | Setting TypeDetectionScheme to None will return all columns as the string type. |
RowScan | Setting TypeDetectionScheme to RowScan will scan rows to heuristically determine the data type. The RowScanDepth determines the number of rows to be scanned. |