`"listTransforms"`

Abstract

listTransforms obtains a list of the names of existing transforms.

The "listTransforms" action obtains a list of the names of existing transforms.

Things to know

Use the "partialName" property to filter the list by partial names.
You can include additional items in the list by searching for words contained in the item’s metadata.
Use "describeTransforms" to get detailed information about specific transforms.

Request examples

Minimal request example

{
    "api": "hub",
    "apiVersion": "1.0",
    "action": "listTransforms",
    "params": {},
    "authToken": "aAuthorizedTokenFromServer",
    "requestId": "00000011"
}

Maximal request example

{
    "api": "hub",
    "apiVersion": "1.0",
    "action": "listTransforms",
    "params": {
        "partialName": "Sensor",
        "skipRecords": 0,
        "maxRecords": 20
    },
    "authToken": "aAuthorizedTokenFromServer",
    "requestId": "00000012"
}

Response examples

Minimal response example

{
    "result": {
        "data": [
            "SensorsTransform1"
        ]
    },
    "requestId": "00000011",
    "errorCode": 0,
    "errorMessage": ""
}

Maximal response example

{
    "result": {
        "data": [
            "SensorsTransform1"
        ]
    },
    "requestId": "00000012",
    "errorCode": 0,
    "errorMessage": ""
}

`"params"`

The "params" property is an object that contains an action's parameters. Each action defines its own required and optional properties.

Properties summary

Table 1. "params" properties summary

Property

Description

Default

Type

Limits (inclusive)

databaseName

specifies the name of a database

Defaults to the "defaultDatabaseName" value that is set during "createSession". If no default is set during "createSession", then "faircom" is used.

string

1 to 64 bytes

dataFormat

specifies the returned results as an array of array, an array of objects, or the default setting defined at login

"arrays"

string

"autoDetect"

"arrays"

"objects"

maxRecords

specifies the maximum number of records to return from an action

20

integer

-1 to 65535

ownerName

specifies the unique name of a schema in a database

""

string

1 to 64 bytes

partialName

filters the returned topics by applying partial matches to their names

""

string

0 to 64 bytes

search

searches the content of the "metadata" property that is part of each topic and integration table

""

string

0 to 64 bytes

skipRecords

specifies the number of records to skip over in the results before returning records

0

integer

0 to 9223372036854775807

`"databaseName"`

The "databaseName" property is an optional string that specifies the database that contains the tables. It defaults to the database name supplied at login.

Note

In the API Explorer, "defaultDatabaseName" is set to "ctreeSQL" in the "createSession" action that happens at login.

Things to know:

A zero-length "databaseName" is invalid.
Its limits are from 0 to 64 bytes.
If the "databaseName" property is omitted or set to null, the server will use the default database name specified at login.
If no default database is specified during "createSession", "defaultDatabaseName" will be set to the "defaultDatabaseName" value that is specified in the services.json file.

`"dataFormat"`

The "dataFormat" property is an optional, case-insensitive string enum that defines the format of the response in the "data" property. The default format is an array of arrays. The alternative is an array of objects. The default for "dataFormat" can be changed during a "createSession" action by assigning a different value to the "dataFormat" property in "defaultResponseOptions".

There are three different (but similar) versions of the "dataFormat" property:

Two of those versions occur in a request and another occurs in a response. They all indicate how data is formatted.

"dataFormat" in the request inside "responseOptions" determines how the "data" property in the response is formatted.
Possible values include:
- "arrays"
  This is the default and causes the server to return results as an array of arrays, which is the most efficient.
- "objects"
  This returns results as an array of objects. This is less efficient but is simpler to generate, read, and troubleshoot.
"dataFormat" in the request in the "params" object notifies the server how the "sourceData" property is formatted in the request. This version is rarely used because of the default "autoDetect" behavior.
Possible values include:
- "arrays"
  This causes the server to return results as an array of arrays, which is the most efficient.
- "objects"
  This returns results as an array of objects. This is less efficient but is simpler to generate, read, and troubleshoot.
- "autoDetect"
  This is the default and causes the server to automatically detect the format of the data in the "sourceData" property.
"dataFormat" in the response shows the client how the server formatted the "data" property.
Possible values include:
- "arrays"
  This is the default and causes the server to return results as an array of arrays, which is the most efficient.
- "objects"
  This returns results as an array of objects. This is less efficient but is simpler to generate, read, and troubleshoot.

`"maxRecords"`

The "maxRecords" is an optional integer from -1 to 65,535 that sets the maximum number of records to return from an action. It is used in query actions to paginate the query results when returning records directly. The default for most actions is to return 20 records.

Important

-1 returns all records and should be used very carefully because a large query can return so many records that it eventually times out and wastes server and client resources.

Things to know:

When present, "maxRecords" works in conjunction with the "skipRecords" (and, when applicable, "reverseOrder") properties to paginate results.
"maxRecords" returns an error when "returnCursor" is true.
Note
This does not apply to the actions where "returnCursor" is not present.
When returning a cursor, retrieve records using the "getRecordsFromCursor" action.
A value of 0 for "maxRecords" is not useful because it causes the action to return no records.
"maxRecords" is ignored by the "getRecordsByIds" action.

`"ownerName"`

The "ownerName" property is an optional string from 1 to 64 bytes that specifies the account that owns an object.

Things to know:

The "ownerName" property is optional and has a dynamic default value.
If the "ownerName" property is omitted or set to null, the server uses the value of the "defaultOwnerName" property supplied during the "createSession" action.
If the "defaultOwnerName" property is not defined, the server uses the "admin" as the owner name.
The owner of an object has administrative rights over that object.
The "ownerName" property is a namespace for an object. You can think of it as a container of objects.
The "ownerName" allows users to use any name for the objects they create — for example, a QA engineer may copy tables into their owner space to run a set of tests.
It is common for a user to create their own copies of objects from other accounts for testing, troubleshooting, and fixing data. The copied objects can retain the same name because the "ownerName" distinguishes between them.
The fully qualified name of an object is the "databaseName", "ownerName", and the object's name, such as "tableName" meaning a FairCom server may contain many tables with the name "mytable" as long as each one is in a different database or in a different owner space.
For example, an organization often creates different databases for different phases of the development lifecycle, such as dev, test, stage, ua, and prod. Each of these databases contains the same set of objects with the same names. Applications leave the "databaseName" out of their JSON actions and use the "defaultDatabaseName" property to specify the target database.
Queries and scripts are often written without specifying "databaseName" and/or "ownerName", allowing queries and scripts to work properly when run in different databases or in different schemas.

`"partialName"`

The "partialName" property is an optional string that causes the server to include items in the result when the beginning of their names match the "partialName" value. It defaults to an empty string.

Things to know:

A zero-length string matches all names.
The "partialName" property is used to filter results in several actions used to return lists.

`"search"`

The "search" property is an optional string that searches the content of the "metadata" property that is part of each topic and integration table.

Things to know:

If there is nothing in the "metadata" property for a topic or an integration table, there is nothing to search for, resulting in an empty array in the "data" property in the response.
The "metadata" property is a JSON field, meaning you can put a valid JSON in it — for example, a string or object.

`"skipRecords"`

The "skipRecords" property is an optional integer from 0 to 9,223,372,036,854,775,807. It is used in query actions to paginate the query results when returning records directly. It defaults to 0.

Things to know:

It specifies the number of records to skip over in the results before returning records.
It works with "maxRecords" and "reverseOrder".
It is ignored when "returnCursor" is true.
Note
This does not apply to the actions where "returnCursor" is not present.

`"result"`

Properties summary

Table 2. "result" properties summary

Property	Description	Type	Limits (inclusive)
data	specifies an array or object that the server returns, such as records returned by a query Note It is an empty array when there are no results available.	array	Its contents are determined by the action