CData Cloud offers access to Asana 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 Asana through CData Cloud.
CData Cloud allows you to standardize and configure connections to Asana as though it were any other OData endpoint, or standard SQL Server/MySQL database.
This page provides a guide to Establishing a Connection to Asana 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 Asana and configure any necessary connection properties to create a database in CData Cloud
Accessing data from Asana through the available standard services and CData Cloud administration is documented in further details in the CData Cloud Documentation.
Connect to Asana 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.
You can optionally set the following to refine the data returned from Asana.
Asana uses the OAuth authentication standard.
AuthScheme must be set to OAuth in all user account flows.
To obtain an OAuthClientId, OAuthClientSecret, and CallbackURL, you first need to create an app linked to your Asana account.
To create an app linked to your Asana account:
Once you are done with creating a new app, it will be displayed on your screen. From there, you can click View Client ID to reveal your newly created app's OAuthClientId and OAuthClientSecret.
Date | Build Number | Change Type | Description |
12/14/2022 | 8383 | General | Changed
|
09/30/2022 | 8308 | General | Changed
|
08/18/2022 | 8265 | Asana | Added
Modified
|
08/17/2022 | 8264 | General | Changed
|
07/07/2022 | 8223 | Asana | Added
|
06/13/2022 | 8199 | Asana | Added
|
05/16/2022 | 8171 | Asana | Added
|
04/18/2022 | 8143 | Asana | Added
|
09/02/2021 | 7915 | General | Added
|
08/07/2021 | 7889 | General | Changed
|
08/06/2021 | 7888 | General | Changed
|
07/23/2021 | 7874 | General | Changed
|
07/08/2021 | 7859 | General | Added
|
04/23/2021 | 7785 | General | Added
|
04/23/2021 | 7783 | General | Changed
|
04/16/2021 | 7776 | General | Added
Changed
|
04/15 /2021 | 7775 | General | Changed
|
This section details a selection of advanced features of the Asana Cloud.
The Cloud allows you to define virtual tables, called user defined views, whose contents are decided by a pre-configured query. These views are useful when you cannot directly control queries being issued to the drivers. See User Defined Views for an overview of creating and configuring custom views.
Use SSL Configuration to adjust how Cloud handles TLS/SSL certificate negotiations. You can choose from various certificate formats; see the SSLServerCert property under "Connection String Options" for more information.
Configure the Cloud for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.
The Cloud offloads as much of the SELECT statement processing as possible to Asana and then processes the rest of the query in memory (client-side).
See Query Processing for more information.
See Logging for an overview of configuration settings that can be used to refine CData logging. For basic logging, you only need to set two connection properties, but there are numerous features that support more refined logging, where you can select subsets of information to be logged using the LogModules connection property.
The CData Cloud allows you to define a virtual table whose contents are decided by a pre-configured query. These are called User Defined Views, which are useful in situations where you cannot directly control the query being issued to the driver, e.g. when using the driver from a tool. The User Defined Views can be used to define predicates that are always applied. If you specify additional predicates in the query to the view, they are combined with the query already defined as part of the view.
There are two ways to create user defined views:
You can also have multiple view definitions and control them using the UserDefinedViews connection property. When you use this property, only the specified views are seen by the Cloud.
This User Defined View configuration file is formatted as follows:
For example:
{ "MyView": { "query": "SELECT * FROM projects WHERE MyColumn = 'value'" }, "MyView2": { "query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)" } }Use the UserDefinedViews connection property to specify the location of your JSON configuration file. For example:
"UserDefinedViews", "C:\\Users\\yourusername\\Desktop\\tmp\\UserDefinedViews.json"
SELECT * FROM Customers WHERE City = 'Raleigh';An example of a query to the driver:
SELECT * FROM UserViews.RCustomers WHERE Status = 'Active';Resulting in the effective query to the source:
SELECT * FROM Customers WHERE City = 'Raleigh' AND Status = 'Active';That is a very simple example of a query to a User Defined View that is effectively a combination of the view query and the view definition. It is possible to compose these queries in much more complex patterns. All SQL operations are allowed in both queries and are combined when appropriate.
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:
For sources that do not support SQL-92, the Cloud offloads as much of SQL statement processing as possible to Asana and then processes the rest of the query in memory (client-side). This results in optimal performance.
For data sources with limited query capabilities, the Cloud handles transformations of the SQL query to make it simpler for the Cloud. The goal is to make smart decisions based on the query capabilities of the data source to push down as much of the computation as possible. The Asana Query Evaluation component examines SQL queries and returns information indicating what parts of the query the Cloud is not capable of executing natively.
The Asana Query Slicer component is used in more specific cases to separate a single query into multiple independent queries. The client-side Query Engine makes decisions about simplifying queries, breaking queries into multiple queries, and pushing down or computing aggregations on the client-side while minimizing the size of the result set.
There's a significant trade-off in evaluating queries, even partially, client-side. There are always queries that are impossible to execute efficiently in this model, and some can be particularly expensive to compute in this manner. CData always pushes down as much of the query as is feasible for the data source to generate the most efficient query possible and provide the most flexible query capabilities.
Capturing Cloud logging can be very helpful when diagnosing error messages or other unexpected behavior.
You will simply need to set two connection properties to begin capturing Cloud logging.
Once this property is set, the Cloud will populate the log file as it carries out various tasks, such as when authentication is performed or queries are executed. If the specified file doesn't already exist, it will be created.
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 described in the following list:
1 | Setting Verbosity to 1 will log the query, the number of rows returned by it, the start of execution and the time taken, and any errors. |
2 | Setting Verbosity to 2 will log everything included in Verbosity 1 and additional information about the request. |
3 | Setting Verbosity to 3 will additionally log HTTP headers, as well as the body of the request and the response. |
4 | Setting Verbosity to 4 will additionally log transport-level communication with the data source. This includes SSL negotiation. |
5 | Setting Verbosity to 5 will additionally log communication with the data source and additional details that may be helpful in troubleshooting problems. This includes interface commands. |
The Verbosity should not be set to greater than 1 for normal operation. Substantial amounts of data can be logged at higher verbosities, which can delay execution times.
To refine the logged content further by showing/hiding specific categories of information, see LogModules.
Best Practices for Data Security
Although we mask sensitive values, such as passwords, in the connection string and any request in the log, it is always best practice to review the logs for any sensitive information before sharing outside your organization.
You may want to refine the exact information that is recorded to the log file. This can be accomplished using the LogModules property.
This property allows you to filter the logging using a semicolon-separated list of logging modules.
All modules are four characters long. Please note that modules containing three letters have a required trailing blank space. The available modules are:
LogModules=INFO;EXEC;SSL ;SQL ;META;
Note that these modules refine the information as it is pulled after taking the Verbosity into account.
The CData Cloud supports several operations on data, including querying, deleting, modifying, and inserting.
See SELECT Statements for a syntax reference and examples.
See Data Model for information on the capabilities of the Asana API.
See INSERT Statements for a syntax reference and examples.
The primary key Id is required to update a record. See UPDATE Statements for a syntax reference and examples.
The primary key Id is required to delete a record. See DELETE Statements for a syntax reference and examples.
Use EXECUTE or EXEC statements to execute stored procedures. See EXECUTE Statements for a syntax reference and examples.
A SELECT statement can consist of the following basic clauses.
The following syntax diagram outlines the syntax supported by the SQL engine of the Cloud:
SELECT {
[ TOP <numeric_literal> | DISTINCT ]
{
*
| {
<expression> [ [ AS ] <column_reference> ]
| { <table_name> | <correlation_name> } .*
} [ , ... ]
}
[ INTO csv:// [ filename= ] <file_path> [ ;delimiter=tab ] ]
{
FROM <table_reference> [ [ AS ] <identifier> ]
} [ , ... ]
[ [
INNER | { { LEFT | RIGHT | FULL } [ OUTER ] }
] JOIN <table_reference> [ ON <search_condition> ] [ [ AS ] <identifier> ]
] [ ... ]
[ WHERE <search_condition> ]
[ GROUP BY <column_reference> [ , ... ]
[ HAVING <search_condition> ]
[ UNION [ ALL ] <select_statement> ]
[
ORDER BY
<column_reference> [ ASC | DESC ] [ NULLS FIRST | NULLS LAST ]
]
[
LIMIT <expression>
[
{ OFFSET | , }
<expression>
]
]
} | SCOPE_IDENTITY()
<expression> ::=
| <column_reference>
| @ <parameter>
| ?
| COUNT( * | { [ DISTINCT ] <expression> } )
| { AVG | MAX | MIN | SUM | COUNT } ( <expression> )
| NULLIF ( <expression> , <expression> )
| COALESCE ( <expression> , ... )
| CASE <expression>
WHEN { <expression> | <search_condition> } THEN { <expression> | NULL } [ ... ]
[ ELSE { <expression> | NULL } ]
END
| <literal>
| <sql_function>
<search_condition> ::=
{
<expression> { = | > | < | >= | <= | <> | != | LIKE | NOT LIKE | IN | NOT IN | IS NULL | IS NOT NULL | AND | OR | CONTAINS | BETWEEN } [ <expression> ]
} [ { AND | OR } ... ]
SELECT * FROM projects
SELECT [WorkspaceId] AS MY_WorkspaceId FROM projects
SELECT CAST(AnnualRevenue AS VARCHAR) AS Str_AnnualRevenue FROM projects
SELECT * FROM projects WHERE Archived = 'true'
SELECT COUNT(*) AS MyCount FROM projects
SELECT COUNT(DISTINCT WorkspaceId) FROM projects
SELECT DISTINCT WorkspaceId FROM projects
SELECT WorkspaceId, MAX(AnnualRevenue) FROM projects GROUP BY WorkspaceIdSee Aggregate Functions for details.
SELECT P.Id,P.Name,P.color,PS.Id,PS.Title FROM Projects P INNER JOIN ProjectStatuses PS ON P.Id=PS.ProjectIdSee JOIN Queries for details.
SELECT Id, WorkspaceId FROM projects ORDER BY WorkspaceId ASC
SELECT Id, WorkspaceId FROM projects LIMIT 10
SELECT * FROM projects WHERE Archived = @param
Some input-only fields are available in SELECT statements. These fields, called pseudo columns, do not
appear as regular columns in the results, yet may be specified as part of the WHERE clause. You can use pseudo columns to access additional features from Asana.
SELECT * FROM projects WHERE Query = 'Column3 > 100'
Returns the number of rows matching the query criteria.
SELECT COUNT(*) FROM projects WHERE Archived = 'true'
Returns the number of distinct, non-null field values matching the query criteria.
SELECT COUNT(DISTINCT Id) AS DistinctValues FROM projects WHERE Archived = 'true'
Returns the average of the column values.
SELECT WorkspaceId, AVG(AnnualRevenue) FROM projects WHERE Archived = 'true' GROUP BY WorkspaceId
Returns the minimum column value.
SELECT MIN(AnnualRevenue), WorkspaceId FROM projects WHERE Archived = 'true' GROUP BY WorkspaceId
Returns the maximum column value.
SELECT WorkspaceId, MAX(AnnualRevenue) FROM projects WHERE Archived = 'true' GROUP BY WorkspaceId
Returns the total sum of the column values.
SELECT SUM(AnnualRevenue) FROM projects WHERE Archived = 'true'
The CData Cloud supports standard SQL joins like the following examples.
An inner join selects only rows from both tables that match the join condition:
SELECT P.Id,P.Name,P.color,PS.Id,PS.Title FROM Projects P INNER JOIN ProjectStatuses PS ON P.Id=PS.ProjectId
A left join selects all rows in the FROM table and only matching rows in the JOIN table:
SELECT P.Id,P.Name,P.color,PS.Id,PS.Title FROM Projects P LEFT JOIN ProjectStatuses PS ON P.Id=PS.ProjectId
The following date literal functions can be used to filter date fields using relative intervals. Note that while the <, >, and = operators are supported for these functions, <= and >= are not.
The current day.
SELECT * FROM MyTable WHERE MyDateField = L_TODAY()
The previous day.
SELECT * FROM MyTable WHERE MyDateField = L_YESTERDAY()
The following day.
SELECT * FROM MyTable WHERE MyDateField = L_TOMORROW()
Every day in the preceding week.
SELECT * FROM MyTable WHERE MyDateField = L_LAST_WEEK()
Every day in the current week.
SELECT * FROM MyTable WHERE MyDateField = L_THIS_WEEK()
Every day in the following week.
SELECT * FROM MyTable WHERE MyDateField = L_NEXT_WEEK()Also available:
The previous n days, excluding the current day.
SELECT * FROM MyTable WHERE MyDateField = L_LAST_N_DAYS(3)
The following n days, including the current day.
SELECT * FROM MyTable WHERE MyDateField = L_NEXT_N_DAYS(3)Also available:
Every day in every week, starting n weeks before current week, and ending in the previous week.
SELECT * FROM MyTable WHERE MyDateField = L_LAST_N_WEEKS(3)
Every day in every week, starting the following week, and ending n weeks in the future.
SELECT * FROM MyTable WHERE MyDateField = L_NEXT_N_WEEKS(3)Also available:
You can use the SELECT INTO statement to export formatted data to a file.
The following query exports data into a file formatted in comma-separated values (CSV):
SELECT Id, WorkspaceId INTO [csv://projects.txt] FROM [projects] WHERE Archived = 'true'You can specify other formats in the file URI. The possible delimiters are tab, semicolon, and comma with the default being a comma. The following example exports tab-separated values:
SELECT Id, WorkspaceId INTO [csv://projects.txt;delimiter=tab] FROM [projects] WHERE Archived = 'true'You can specify other file formats in the URI. The following example exports tab-separated values:
The Cloud provides functions that are similar to those that are available with most standard databases. These functions are implemented in the CData provider engine and thus are available across all data sources with the same consistent API. Three categories of functions are available: string, date, and math.
The Cloud interprets all SQL function inputs as either strings or column identifiers, so you need to escape all literals as strings, with single quotes. For example, contrast the SQL Server syntax and Cloud syntax for the DATENAME function:
SELECT DATENAME(yy,GETDATE())
SELECT DATENAME('yy',GETDATE())
These functions perform string manipulations and return a string value. See STRING Functions for more details.
SELECT CONCAT(firstname, space(4), lastname) FROM projects WHERE Archived = 'true'
These functions perform date and date time manipulations. See DATE Functions for more details.
SELECT CURRENT_TIMESTAMP() FROM projects
These functions provide mathematical operations. See MATH Functions for more details.
SELECT RAND() FROM projects
SELECT CONCAT('Mr.', SPACE(2), firstname, SPACE(4), lastname) FROM projects
Returns the ASCII code value of the left-most character of the character expression.
SELECT ASCII('0'); -- Result: 48
Converts the integer ASCII code to the corresponding character.
SELECT CHAR(48); -- Result: '0'
Returns the starting position of the specified expression in the character string.
SELECT CHARINDEX('456', '0123456'); -- Result: 4 SELECT CHARINDEX('456', '0123456', 5); -- Result: -1
Returns the number of UTF-8 characters present in the expression.
SELECT CHAR_LENGTH('sample text') FROM Account LIMIT 1 -- Result: 11
Returns the string that is the concatenation of two or more string values.
SELECT CONCAT('Hello, ', 'world!'); -- Result: 'Hello, world!'
Returns 1 if expressionToFind is found within expressionToSearch; otherwise, 0.
SELECT CONTAINS('0123456', '456'); -- Result: 1 SELECT CONTAINS('0123456', 'Not a number'); -- Result: 0
Returns 1 if character_expression ends with character_suffix; otherwise, 0.
SELECT ENDSWITH('0123456', '456'); -- Result: 1 SELECT ENDSWITH('0123456', '012'); -- Result: 0
Returns the number of bytes present in the file at the specified file path.
SELECT FILESIZE('C:/Users/User1/Desktop/myfile.txt'); -- Result: 23684
Returns the value formatted with the specified format.
SELECT FORMAT(12.34, '#'); -- Result: 12 SELECT FORMAT(12.34, '#.###'); -- Result: 12.34 SELECT FORMAT(1234, '0.000E0'); -- Result: 1.234E3 SELECT FORMAT('2019/01/01', 'yyyy-MM-dd'); -- Result: 2019-01-01 SELECT FORMAT('20190101', 'yyyyMMdd', 'yyyy-MM-dd'); -- Result: '2019-01-01'
Returns a representation of the unix_timestamp argument as a value in YYYY-MM-DD HH:MM:SS expressed in the current time zone.
SELECT FROM_UNIXTIME(1540495231, 1); -- Result: 2018-10-25 19:20:31 SELECT FROM_UNIXTIME(1540495357385, 0); -- Result: 2018-10-25 19:22:37
Returns the hash of the input value as a byte array using the given algorithm. The supported algorithms are MD5, SHA1, SHA2_256, SHA2_512, SHA3_224, SHA3_256, SHA3_384, and SHA3_512.
SELECT HASHBYTES('MD5', 'Test'); -- Result (byte array): 0x0CBC6611F5540BD0809A388DC95A615B
Returns the starting position of the specified expression in the character string.
SELECT INDEXOF('0123456', '456'); -- Result: 4 SELECT INDEXOF('0123456', '456', 5); -- Result: -1
Replaces null with the specified replacement value.
SELECT ISNULL(42, 'Was NULL'); -- Result: 42 SELECT ISNULL(NULL, 'Was NULL'); -- Result: 'Was NULL'
Computes the average value of a JSON array within a JSON object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_AVG('[1,2,3,4,5]', '$[x]'); -- Result: 3 SELECT JSON_AVG('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 3 SELECT JSON_AVG('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[3..]'); -- Result: 4.5
Returns the number of elements in a JSON array within a JSON object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_COUNT('[1,2,3,4,5]', '$[x]'); -- Result: 5 SELECT JSON_COUNT('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 5 SELECT JSON_COUNT('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[3..]'); -- Result: 2
Selects any value in a JSON array or object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_EXTRACT('{"test": {"data": 1}}', '$.test'); -- Result: '{"data":1}' SELECT JSON_EXTRACT('{"test": {"data": 1}}', '$.test.data'); -- Result: 1 SELECT JSON_EXTRACT('{"test": {"data": [1, 2, 3]}}', '$.test.data[1]'); -- Result: 2
Gets the maximum value in a JSON array within a JSON object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_MAX('[1,2,3,4,5]', '$[x]'); -- Result: 5 SELECT JSON_MAX('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 5 SELECT JSON_MAX('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[..3]'); -- Result: 4
Gets the minimum value in a JSON array within a JSON object. The path to the array is specified in the jsonpath argument. Return value is numeric or null.
SELECT JSON_MIN('[1,2,3,4,5]', '$[x]'); -- Result: 1 SELECT JSON_MIN('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 1 SELECT JSON_MIN('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[3..]'); -- Result: 4
Computes the summary value in JSON according to the JSONPath expression. Return value is numeric or null.
SELECT JSON_SUM('[1,2,3,4,5]', '$[x]'); -- Result: 15 SELECT JSON_SUM('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[x]'); -- Result: 15 SELECT JSON_SUM('{"test": {"data": [1,2,3,4,5]}}', '$.test.data[3..]'); -- Result: 9
Returns the specified number of characters counting from the left of the specified string.
SELECT LEFT('1234567890', 3); -- Result: '123'
Returns the number of characters of the specified string expression.
SELECT LEN('12345'); -- Result: 5
Returns an integer representing how many characters into the string the substring appears.
SELECT LOCATE('sample','XXXXXsampleXXXXX'); -- Result: 6
Returns the character expression with the uppercase character data converted to lowercase.
SELECT LOWER('MIXED case'); -- Result: 'mixed case'
Returns the character expression with leading blanks removed.
SELECT LTRIM(' trimmed'); -- Result: 'trimmed'
Replaces the characters between start_index and end_index with the mask_character within the string.
SELECT MASK('1234567890','*',); -- Result: '**********' SELECT MASK('1234567890','*', 4); -- Result: '1234******' SELECT MASK('1234567890','*', 4, 2); -- Result: '1234****90'
Returns the Unicode character with the specified integer code as defined by the Unicode standard.
Returns the number of bytes present in the expression.
SELECT OCTET_LENGTH('text') FROM Account LIMIT 1 -- Result: 4
Returns the starting position of the first occurrence of the pattern in the expression. Returns 0 if the pattern is not found.
SELECT PATINDEX('123%', '1234567890'); -- Result: 1 SELECT PATINDEX('%890', '1234567890'); -- Result: 8 SELECT PATINDEX('%456%', '1234567890'); -- Result: 4
Returns the starting position of the specified expression in the character string.
SELECT POSITION('456' IN '123456'); -- Result: 4 SELECT POSITION('x' IN '123456'); -- Result: 0
Returns a valid SQL Server-delimited identifier by adding the necessary delimiters to the specified Unicode string.
SELECT QUOTENAME('table_name'); -- Result: '[table_name]' SELECT QUOTENAME('table_name', '"'); -- Result: '"table_name"' SELECT QUOTENAME('table_name', '['); -- Result: '[table_name]'
Replaces all occurrences of a string with another string.
SELECT REPLACE('1234567890', '456', '|'); -- Result: '123|7890' SELECT REPLACE('123123123', '123', '.'); -- Result: '...' SELECT REPLACE('1234567890', 'a', 'b'); -- Result: '1234567890'
Repeats the string value the specified number of times.
SELECT REPLACE('x', 5); -- Result: 'xxxxx'
Returns the reverse order of the string expression.
SELECT REVERSE('1234567890'); -- Result: '0987654321'
Returns the right part of the string with the specified number of characters.
SELECT RIGHT('1234567890', 3); -- Result: '890'
Returns the character expression after it removes trailing blanks.
SELECT RTRIM('trimmed '); -- Result: 'trimmed'
Returns the four-character Soundex code, based on how the string sounds when spoken.
SELECT SOUNDEX('smith'); -- Result: 'S530'
Returns the string that consists of repeated spaces.
SELECT SPACE(5); -- Result: ' '
Returns a section of the string between to delimiters.
SELECT SPLIT('a/b/c/d', '/', 1); -- Result: 'a' SELECT SPLIT('a/b/c/d', '/', -2); -- Result: 'c'
Returns 1 if character_expression starts with character_prefix; otherwise, 0.
SELECT STARTSWITH('0123456', '012'); -- Result: 1 SELECT STARTSWITH('0123456', '456'); -- Result: 0
Returns the character data converted from the numeric data. For example, STR(123.45, 6, 1) returns 123.5.
SELECT STR('123.456'); -- Result: '123' SELECT STR('123.456', 2); -- Result: '**' SELECT STR('123.456', 10, 2); -- Result: '123.46'
Inserts a string into another string. It deletes the specified length of characters in the first string at the start position and then inserts the second string into the first string at the start position.
SELECT STUFF('1234567890', 3, 2, 'xx'); -- Result: '12xx567890'
Returns the part of the string with the specified length; starts at the specified index.
SELECT SUBSTRING('1234567890' FROM 3 FOR 2); -- Result: '34' SELECT SUBSTRING('1234567890' FROM 3); -- Result: '34567890'
Converts the value of this instance to its equivalent string representation.
SELECT TOSTRING(123); -- Result: '123' SELECT TOSTRING(123.456); -- Result: '123.456' SELECT TOSTRING(null); -- Result: ''
Returns the character expression with leading and/or trailing blanks removed.
SELECT TRIM(' trimmed '); -- Result: 'trimmed' SELECT TRIM(LEADING FROM ' trimmed '); -- Result: 'trimmed ' SELECT TRIM('-' FROM '-----trimmed-----'); -- Result: 'trimmed' SELECT TRIM(BOTH '-' FROM '-----trimmed-----'); -- Result: 'trimmed' SELECT TRIM(TRAILING '-' FROM '-----trimmed-----'); -- Result: '-----trimmed'
Returns the integer value defined by the Unicode standard of the first character of the input expression.
Returns the character expression with lowercase character data converted to uppercase.
SELECT UPPER('MIXED case'); -- Result: 'MIXED CASE'
Extracts an XML document using the specified XPath to flatten the XML. A comma is used to separate the outputs by default, but this can be changed by specifying the third parameter.
SELECT XML_EXTRACT('<vowels><ch>a</ch><ch>e</ch><ch>i</ch><ch>o</ch><ch>u</ch></vowels>', '/vowels/ch'); -- Result: 'a,e,i,o,u' SELECT XML_EXTRACT('<vowels><ch>a</ch><ch>e</ch><ch>i</ch><ch>o</ch><ch>u</ch></vowels>', '/vowels/ch', ';'); -- Result: 'a;e;i;o;u'
Returns the current date value.
SELECT CURRENT_DATE(); -- Result: 2018-02-01
Returns the current time stamp of the database system as a datetime value. This value is equal to GETDATE and SYSDATETIME, and is always in the local timezone.
SELECT CURRENT_TIMESTAMP(); -- Result: 2018-02-01 03:04:05
Returns the datetime value that results from adding the specified number (a signed integer) to the specified date part of the date.
SELECT DATEADD('d', 5, '2018-02-01'); -- Result: 2018-02-06 SELECT DATEADD('hh', 5, '2018-02-01 00:00:00'); -- Result: 2018-02-01 05:00:00
Returns the difference (a signed integer) of the specified time interval between the specified start date and end date.
SELECT DATEDIFF('d', '2018-02-01', '2018-02-10'); -- Result: 9 SELECT DATEDIFF('hh', '2018-02-01 00:00:00', '2018-02-01 12:00:00'); -- Result: 12
Returns the datetime value for the specified year, month, and day.
SELECT DATEFROMPARTS(2018, 2, 1); -- Result: 2018-02-01
Returns the character string that represents the specified date part of the specified date.
SELECT DATENAME('yy', '2018-02-01'); -- Result: '2018' SELECT DATENAME('dw', '2018-02-01'); -- Result: 'Thursday'
Returns a character string that represents the specified date part of the specified date.
SELECT DATEPART('yy', '2018-02-01'); -- Result: 2018 SELECT DATEPART('dw', '2018-02-01'); -- Result: 5
Returns the datetime value for the specified date parts.
SELECT DATETIME2FROMPARTS(2018, 2, 1, 1, 2, 3, 456, 3); -- Result: 2018-02-01 01:02:03.456
Returns the datetime value for the specified date parts.
SELECT DATETIMEFROMPARTS(2018, 2, 1, 1, 2, 3, 456); -- Result: 2018-02-01 01:02:03.456
Truncates the date to the precision of the given date part. Modeled after the Oracle TRUNC function.
SELECT DATE_TRUNC('05-04-2005', 'YY'); -- Result: '1/1/2005' SELECT DATE_TRUNC('05-04-2005', 'MM'); -- Result: '5/1/2005'
Truncates the date to the precision of the given date part. Modeled after the PostgreSQL date_trunc function.
SELECT DATE_TRUNC2('year', '2020-02-04'); -- Result: '2020-01-01' SELECT DATE_TRUNC2('week', '2020-02-04', 'monday'); -- Result: '2020-02-02', which is the previous Monday
Returns the integer that specifies the day component of the specified date.
SELECT DAY('2018-02-01'); -- Result: 1
SELECT DAYOFMONTH('04/15/2000'); -- Result: 15
SELECT DAYOFWEEK('04/15/2000'); -- Result: 7
SELECT DAYOFYEAR('04/15/2000'); -- Result: 106
Returns the last day of the month that contains the specified date with an optional offset.
SELECT EOMONTH('2018-02-01'); -- Result: 2018-02-28 SELECT LAST_DAY('2018-02-01'); -- Result: 2018-02-28 SELECT EOMONTH('2018-02-01', 2); -- Result: 2018-04-30
SELECT FDWEEK('02-08-2018'); -- Result: 2/4/2018
SELECT FDMONTH('02-08-2018'); -- Result: 2/1/2018
SELECT FDQUARTER('05-08-2018'); -- Result: 4/1/2018
Returns the time stamp associated with the Date Modified of the relevant file.
SELECT FILEMODIFIEDTIME('C:/Documents/myfile.txt'); -- Result: 6/25/2019 10:06:58 AM
Returns a date derived from the number of days after 1582-10-15 (based upon the Gregorian calendar). This will be equivalent to the MYSQL FROM_DAYS function.
SELECT FROM_DAYS(736000); -- Result: 2/6/2015
Returns the current time stamp of the database system as a datetime value. This value is equal to CURRENT_TIMESTAMP and SYSDATETIME, and is always in the local timezone.
SELECT GETDATE(); -- Result: 2018-02-01 03:04:05
Returns the current time stamp of the database system formatted as a UTC datetime value. This value is equal to SYSUTCDATETIME.
SELECT GETUTCDATE(); -- For example, if the local timezone is Eastern European Time (GMT+2) -- Result: 2018-02-01 05:04:05
Returns the hour component from the provided datetime.
SELECT HOUR('02-02-2020 11:30:00'); -- Result: 11
Returns 1 if the value is a valid date, time, or datetime value; otherwise, 0.
SELECT ISDATE('2018-02-01', 'yyyy-MM-dd'); -- Result: 1 SELECT ISDATE('Not a date'); -- Result: 0
Returns a time stamp equivalent to exactly one week before the current date.
SELECT LAST_WEEK(); //Assume the date is 3/17/2020 -- Result: 3/10/2020
Returns a time stamp equivalent to exactly one month before the current date.
SELECT LAST_MONTH(); //Assume the date is 3/17/2020 -- Result: 2/17/2020
Returns a time stamp equivalent to exactly one year before the current date.
SELECT LAST_YEAR(); //Assume the date is 3/17/2020 -- Result: 3/10/2019
Returns the last day of the provided week.
SELECT LDWEEK('02-02-2020'); -- Result: 2/8/2020
Returns the last day of the provided month.
SELECT LDMONTH('02-02-2020'); -- Result: 2/29/2020
Returns the last day of the provided quarter.
SELECT LDQUARTER('02-02-2020'); -- Result: 3/31/2020
Returns a date value from a year and a number of days.
SELECT MAKEDATE(2020, 1); -- Result: 2020-01-01
Returns the minute component from the provided datetime.
SELECT MINUTE('02-02-2020 11:15:00'); -- Result: 15
Returns the month component from the provided datetime.
SELECT MONTH('02-02-2020'); -- Result: 2
Returns the quarter associated with the provided datetime.
SELECT QUARTER('02-02-2020'); -- Result: 1
Returns the second component from the provided datetime.
SELECT SECOND('02-02-2020 11:15:23'); -- Result: 23
Returns the datetime value for the specified date and time.
SELECT SMALLDATETIMEFROMPARTS(2018, 2, 1, 1, 2); -- Result: 2018-02-01 01:02:00
Parses the provided string value and returns the corresponding datetime.
SELECT STRTODATE('03*04*2020','dd*MM*yyyy'); -- Result: 4/3/2020
Returns the current time stamp as a datetime value of the database system. It is equal to GETDATE and CURRENT_TIMESTAMP, and is always in the local timezone.
SELECT SYSDATETIME(); -- Result: 2018-02-01 03:04:05
Returns the current system date and time as a UTC datetime value. It is equal to GETUTCDATE.
SELECT SYSUTCDATETIME(); -- For example, if the local timezone is Eastern European Time (GMT+2) -- Result: 2018-02-01 05:04:05
Returns the time value for the specified time and with the specified precision.
SELECT TIMEFROMPARTS(1, 2, 3, 456, 3); -- Result: 01:02:03.456
Returns the number of days since 0000-00-01. This will only return a value for dates on or after 1582-10-15 (based upon the Gregorian calendar). This will be equivalent to the MYSQL TO_DAYS function.
SELECT TO_DAYS('02-06-2015'); -- Result: 736000
Returns the week (of the year) associated with the provided datetime.
SELECT WEEK('02-17-2020 11:15:23'); -- Result: 8
Returns the integer that specifies the year of the specified date.
SELECT YEAR('2018-02-01'); -- Result: 2018
Returns the absolute (positive) value of the specified numeric expression.
SELECT ABS(15); -- Result: 15 SELECT ABS(-15); -- Result: 15
Returns the arc cosine, the angle in radians whose cosine is the specified float expression.
SELECT ACOS(0.5); -- Result: 1.0471975511966
Returns the arc sine, the angle in radians whose sine is the specified float expression.
SELECT ASIN(0.5); -- Result: 0.523598775598299
Returns the arc tangent, the angle in radians whose tangent is the specified float expression.
SELECT ATAN(10); -- Result: 1.47112767430373
Returns the angle in radians between the positive x-axis and the ray from the origin to the point (y, x) where x and y are the values of the two specified float expressions.
SELECT ATN2(1, 1); -- Result: 0.785398163397448
Returns the smallest integer greater than or equal to the specified numeric expression.
SELECT CEILING(1.3); -- Result: 2 SELECT CEILING(1.5); -- Result: 2 SELECT CEILING(1.7); -- Result: 2
Returns the trigonometric cosine of the specified angle in radians in the specified expression.
SELECT COS(1); -- Result: 0.54030230586814
Returns the trigonometric cotangent of the angle in radians specified by float_expression.
SELECT COT(1); -- Result: 0.642092615934331
Returns the angle in degrees for the angle specified in radians.
SELECT DEGREES(3.1415926); -- Result: 179.999996929531
Returns the exponential value of the specified float expression. For example, EXP(LOG(20)) is 20.
SELECT EXP(2); -- Result: 7.38905609893065
Evaluates the expression.
SELECT EXPR('1 + 2 * 3'); -- Result: 7 SELECT EXPR('1 + 2 * 3 == 7'); -- Result: true
Returns the largest integer less than or equal to the numeric expression.
SELECT FLOOR(1.3); -- Result: 1 SELECT FLOOR(1.5); -- Result: 1 SELECT FLOOR(1.7); -- Result: 1
Returns the greatest of the supplied integers.
SELECT GREATEST(3,5,8,10,1) -- Result: 10
Returns a the equivalent hex for the input value.
SELECT HEX(866849198); -- Result: 33AB11AE SELECT HEX('Sample Text'); -- Result: 53616D706C652054657874
Returns the least of the supplied integers.
SELECT LEAST(3,5,8,10,1) -- Result: 1
Returns the natural logarithm of the specified float expression.
SELECT LOG(7.3890560); -- Result: 1.99999998661119
Returns the base-10 logarithm of the specified float expression.
SELECT LOG10(10000); -- Result: 4
Returns the integer value associated with the remainder when dividing the dividend by the divisor.
SELECT MOD(10,3); -- Result: 1
Returns the opposite to the real number input.
SELECT NEGATE(10); -- Result: -10 SELECT NEGATE(-12.4) --Result: 12.4
Returns the constant value of pi.
SELECT PI() -- Result: 3.14159265358979
Returns the value of the specified expression raised to the specified power.
SELECT POWER(2, 10); -- Result: 1024 SELECT POWER(2, -2); -- Result: 0.25
Returns the angle in radians of the angle in degrees.
SELECT RADIANS(180); -- Result: 3.14159265358979
Returns a pseudorandom float value from 0 through 1, exclusive.
SELECT RAND(); -- This result may be different, since the seed is randomized -- Result: 0.873159630165044 SELECT RAND(1); -- This result will always be the same, since the seed is constant -- Result: 0.248668584157093
Returns the numeric value rounded to the specified length or precision.
SELECT ROUND(1.3, 0); -- Result: 1 SELECT ROUND(1.55, 1); -- Result: 1.6 SELECT ROUND(1.7, 0, 0); -- Result: 2 SELECT ROUND(1.7, 0, 1); -- Result: 1 SELECT ROUND (1.24); -- Result: 1.0
Returns the positive sign (1), 0, or negative sign (-1) of the specified expression.
SELECT SIGN(0); -- Result: 0 SELECT SIGN(10); -- Result: 1 SELECT SIGN(-10); -- Result: -1
Returns the trigonometric sine of the angle in radians.
SELECT SIN(1); -- Result: 0.841470984807897
Returns the square root of the specified float value.
SELECT SQRT(100); -- Result: 10
Returns the square of the specified float value.
SELECT SQUARE(10); -- Result: 100 SELECT SQUARE(-10); -- Result: 100
Returns the tangent of the input expression.
SELECT TAN(1); -- Result: 1.5574077246549
Returns the supplied decimal number truncated to have the supplied decimal precision.
SELECT TRUNC(10.3423,2); -- Result: 10.34
To create new records, use INSERT statements.
The INSERT statement specifies the columns to be inserted and the new column values. You can specify the column values in a comma-separated list in the VALUES clause, as shown in the following example:
INSERT INTO <table_name>
( <column_reference> [ , ... ] )
VALUES
( { <expression> | NULL } [ , ... ] )
<expression> ::=
| @ <parameter>
| ?
| <literal>
The following is an example query:
INSERT INTO projects (WorkspaceId) VALUES ('John')
To modify existing records, use UPDATE statements.
The UPDATE statement takes as input a comma-separated list of columns and new column values as name-value pairs in the SET clause, as shown in the following example:
UPDATE <table_name> SET { <column_reference> = <expression> } [ , ... ] WHERE { Id = <expression> } [ { AND | OR } ... ]
<expression> ::=
| @ <parameter>
| ?
| <literal>
The following is an example query:
UPDATE projects SET WorkspaceId='John' WHERE Id = @myId
To delete information from a table, use DELETE statements.
The DELETE statement requires the table name in the FROM clause and the row's primary key in the WHERE clause, as shown in the following example:
<delete_statement> ::= DELETE FROM <table_name> WHERE { Id = <expression> } [ { AND | OR } ... ]
<expression> ::=
| @ <parameter>
| ?
| <literal>
The following is an example query:
DELETE FROM projects WHERE Id = @myId
To execute stored procedures, you can use EXECUTE or EXEC statements.
EXEC and EXECUTE assign stored procedure inputs, referenced by name, to values or parameter names.
To execute a stored procedure as an SQL statement, use the following syntax:
{ EXECUTE | EXEC } <stored_proc_name>
{
[ @ ] <input_name> = <expression>
} [ , ... ]
<expression> ::=
| @ <parameter>
| ?
| <literal>
Reference stored procedure inputs by name:
EXECUTE my_proc @second = 2, @first = 1, @third = 3;
Execute a parameterized stored procedure statement:
EXECUTE my_proc second = @p1, first = @p2, third = @p3;
PIVOT and UNPIVOT can be used to change a table-valued expression into another table.
"SELECT 'AverageCost' AS Cost_Sorted_By_Production_Days, [0], [1], [2], [3], [4]
FROM
(
SELECT DaysToManufacture, StandardCost
FROM Production.Product
) AS SourceTable
PIVOT
(
AVG(StandardCost)
FOR DaysToManufacture IN ([0], [1], [2], [3], [4])
) AS PivotTable;"
"SELECT VendorID, Employee, Orders
FROM
(SELECT VendorID, Emp1, Emp2, Emp3, Emp4, Emp5
FROM pvt) p
UNPIVOT
(Orders FOR Employee IN
(Emp1, Emp2, Emp3, Emp4, Emp5)
)AS unpvt;"
For further information on PIVOT and UNPIVOT, see FROM clause plus JOIN, APPLY, PIVOT (Transact-SQL)
To perform multiple inserts in a single request to Asana, use the INSERT INTO SELECT syntax to insert a temporary table of data into Asana. This works by first populating a temporary table with the data you are going to submit to Asana. Once you have all of the data you want to insert, the temporary table is then passed into the table in Asana.
The temporary table you are populating is dynamic and is created at run time the first time you insert to it. Temporary tables are denoted by a # appearing in their name. When using a temporary table to insert, the temporary table must be named in the format [TableName]#TEMP, where TableName is the
name of the table you will be inserting to. For example:
INSERT INTO projects#TEMP (WorkspaceId, MyCustomField__c) VALUES ('New projects', '9000'); INSERT INTO projects#TEMP (WorkspaceId, MyCustomField__c) VALUES ('New projects 2', '9001'); INSERT INTO projects#TEMP (WorkspaceId, MyCustomField__c) VALUES ('New projects 3', '9002');
This creates a temporary table called projects#TEMP with two columns and three rows of data. Since type cannot be determined on the temporary table itself, all values are stored in memory as strings. They are later converted to the proper type when they are submitted to the projects table.
Once your temporary table is populated, it is now time to insert to the actual table in Asana. You can do this by performing an INSERT to the actual table and selecting the input data from the temporary table. For example:
INSERT INTO projects (WorkspaceId, MyCustomField__c) SELECT WorkspaceId, MyCustomField__c FROM projects#TEMPIn this example, the full contents of the projects#TEMP table are passed into the projects table. This results in fewer requests being submitted to Asana since multiple inserts may be submitted with each request, which is much better for performance if you have many records to insert.
The results of the query are stored in the LastResultInfo#TEMP temporary table. This table is cleared and repopulated the next time data is modified by passing in a temporary table. Please be aware that the LastResultInfo#TEMP table has no predefined schema. You need to check its metadata at run time before reading data.
Temporary tables only last as long as the connection remains open. When the connection to Asana is closed, all temporary tables are cleared, including the LastResultInfo#TEMP table.
To perform multiple updates in a single request to Asana,first use the INSERT INTO syntax to insert a temporary table of data into Asana. This works by first populating a temporary table with the data you are going to submit to Asana. Once you have all of the data you want to update, use UPDATE SELECT FROM to pass the temporary table data into the table in Asana.
The temporary table you are populating is dynamic and is created at run time the first time you insert to it. Temporary tables are denoted by a # appearing in their name. When using a temporary table to update, the temporary table must be named in the format [TableName]#TEMP, where TableName is the
name of the table you are inserting to. For example:
INSERT INTO projects#TEMP (Id, Name, MyCustomField__c) VALUES ('AX1000001', 'New projects', '9000'); INSERT INTO projects#TEMP (Id, Name, MyCustomField__c) VALUES ('AX1000002', 'New projects 2', '9001'); INSERT INTO projects#TEMP (Id, Name, MyCustomField__c) VALUES ('AX1000003', 'New projects 3', '9002');
This creates a temporary table called projects#TEMP with three columns and three rows of data. Since type cannot be determined on the temporary table itself, all values are stored in memory as strings. The values are later converted to the proper type when they are submitted to the projects table.
Once your temporary table is populated, it is now time to update the actual table in Asana. You can do this by performing an UPDATE to the actual table and selecting the input data from the temporary table. For example:
UPDATE projects (Id, WorkspaceId, MyCustomField__c) SELECT Id, WorkspaceId, MyCustomField__c FROM projects#TEMPIn this example, the full contents of the projects#TEMP table are passed into the projects table. This results in fewer requests being submitted to Asana since multiple updates may be submitted with each request, which is much better for performance if you have many records to update.
The results of the query are stored in the LastResultInfo#TEMP temporary table. This table is cleared and repopulated the next time data is modified by passing in a temporary table. Please be aware that the LastResultInfo#TEMP table has no predefined schema. You need to check its metadata at run time before reading data.
Temporary tables only last as long as the connection remains open. When the connection to Asana is closed, all temporary tables are cleared, including the LastResultInfo#TEMP table.
To perform multiple deletes in a single request to Asana, first use the INSERT INTO syntax to create an in-memory temporary table of data to be deleted. Once you have all of the data you want to delete added to temporary table, use DELETE FROM syntax to delete data from the live table in Asana. This functionality is also available via the standard Batch Processing API available in JDBC.
The temporary table you are populating is dynamic and is created at run time the first time you insert to it. Temporary tables are denoted by a # appearing in their name. When using a temporary table to delete, the temporary table must be named in the format [TableName]#TEMP, where TableName is the
name of the table you are inserting to. For example:
INSERT INTO projects#TEMP (Id) VALUES ('AX1000001'); INSERT INTO projects#TEMP (Id) VALUES ('AX1000002'); INSERT INTO projects#TEMP (Id) VALUES ('AX1000003');
This creates a temporary table called projects#TEMP with one column and three rows of data. Since type cannot be determined on the temporary table itself, all values are stored in memory as strings. They are later converted to the proper type when they are submitted to the projects table.
Once your temporary table is populated, it is now time to insert to the actual table in Asana. You can do this by performing a DELETE from the actual table and selecting the input data from the temporary table. For example:
DELETE FROM projects WHERE EXISTS SELECT Id FROM projects#TEMP
In this example, the full contents of the projects#TEMP table are passed into the projects table. This results in fewer requests being submitted to Asana since multiple deletes may be submitted with each request, which is much better for performance if you have many records to delete.
The results of the query are stored in the LastResultInfo#TEMP temporary table. This table is cleared and repopulated the next time data is modified by passing in a temporary table. Please be aware that the LastResultInfo#TEMP table has no predefined schema. You need to check its metadata at run time before reading data.
Temporary tables only last as long as the connection remains opened. When the connection to Asana is closed, all temporary tables are cleared, including the LastResultInfo#TEMP table.
This section shows the available API objects and provides more information on executing SQL to Asana APIs.
Views describes the available views. Views are statically defined to model Projects, Users, Workspaces, and more.
Stored Procedures are function-like interfaces to Asana. Stored procedures allow you to execute operations to Asana, including downloading documents and moving envelopes.
The Cloud models the data in Asana into a list of tables that can be queried using standard SQL statements.
Generally, querying Asana tables is the same as querying a table in a relational database. Sometimes there are special cases, for example, including a certain column in the WHERE clause might be required to get data for certain columns in the table. This is typically needed for situations where a separate request must be made for each row to get certain columns. These types of situations are clearly documented at the top of the table page linked below.
Name | Description |
Attachments | To Delete and Query from the Attachments in the tasks. |
PortfolioItems | To Create, delete, and Query Items in the Portfolio. |
PortfolioMembership | To Create, Delete and Query memberships in the Portfolio. |
Portfolios | To Create, update, delete, and query from Portfolios table. |
ProjectMembership | To Create, Delete and Query memberships in the Project. |
Projects | To Create, Update, Delete and Query the Projects table. |
ProjectStatuses | To Create, Delete and Query from ProjectStatuses table. A project status is an update on the progress of a particular project, and is sent out to all project followers when created. |
Sections | To Create, Update, Delete, and Query from Sections table. A section is a subdivision of a project that groups tasks together. |
Stories | To Create, Update, Delete and Query from stories table. A story represents an activity associated with an object in the Asana system. Stories are generated by the system whenever users take actions such as creating or assigning tasks, or moving tasks between projects. |
SubTasks | To Create, update, delete, and query from SubTasks table. |
Tags | To Create, Update and Query from Tags table. A tag is a label that can be attached to any task in Asana. It exists in a single workspace. |
Tasks | To Create, Update, Delete and Query from Tasks table. |
TeamMembership | To represents a users connection to a team. |
Teams | A team is used to group related projects and people together within an organization. Each project in an organization is associated with a team. |
WorkspaceMembership | To Create, Delete and Query memberships in the Workspace. |
Workspaces | To Update and Query from Workspaces table. A workspace is the highest-level organizational unit in Asana. All projects and tasks have an associated workspace. |
To Delete and Query from the Attachments in the tasks.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The TaskId or Id is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Attachments WHERE Id = '1134618934491707' SELECT * FROM Attachments WHERE TaskId = '1128092964672854'
Following is an example of how to delete from Attachments table:
DELETE FROM Attachments WHERE Id = '1134618934491707'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the attachment. | |
Name | String | True |
The name of the file. | |
Host | String | True |
The service hosting the attachment. Valid values are asana, dropbox, gdrive and box. | |
CreatedAt | Datetime | True |
The time at which this attachment was uploaded. | |
ViewURL | String | True |
The URL where the attachment can be viewed, which may be friendlier to users in a browser than just directing them to a raw file. | |
DownloadURL | String | True |
May be null if the attachment is hosted by box. If present, this URL may only be valid for 1 hour from the time of retrieval. You should avoid persisting this URL somewhere and just refresh it on demand to ensure you do not keep stale URLs. | |
TaskId | String | True |
Tasks.Id |
The task this attachment is attached to. |
ResourceType | String | True |
The resource type of this resource. |
To Create, delete, and Query Items in the Portfolio.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The PortfolioId is required to make a request and rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM PortfolioItems WHERE PortfolioId = '1173026173301164'
ProjectId and PortfolioId is a mandatory column for inserting into PortfolioItems table. For example:
INSERT INTO PortfolioItems (ProjectId, PortfolioId) VALUES ('1173023668354420', '1173026173301164')
Following is an example of how to delete from PortfolioItems table:
DELETE FROM PortfolioItems WHERE ProjectId = '1173023668354420' AND PortfolioId = '1173026173301164'
Name | Type | ReadOnly | References | Description |
Id | String | True |
Globally unique ID of the Portfolio Item. | |
Name | String | True |
Name of the Item. | |
PortfolioId [KEY] | String | True |
Portfolios.Id |
Globally unique ID of the portfolio. |
OwnerId | String | True |
Globally unique ID of the Owner. | |
StartOn | Date | True |
The day on which work for this project begins, or null if the project has no start date. | |
DueOn | Date | True |
The day on which this project is due. This takes a date with format YYYY-MM-DD. | |
ProjectId [KEY] | String | True |
Projects.Id |
Globally unique ID of the Project. This column is a Pseudocolmn and its used for INSERT and UPDATE. |
To Create, Delete and Query memberships in the Portfolio.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The [WorkspaceId AND UserId] OR PortfolioId OR Id is required to make a request and rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM PortfolioMembership WHERE WorkspaceId='1172686716695308' AND UserId='1172686741877880' SELECT * FROM PortfolioMembership WHERE PortfolioId='1172684730399265' SELECT * FROM PortfolioMembership WHERE Id='1172684730399266'
PortfolioId and UserId is a mandatory column for inserting into PortfolioMembership table. For example:
INSERT INTO PortfolioMembership (PortfolioId, UserId) VALUES ('1172684730399265', '1172686741877880')
Following is an example of how to delete from PortfolioMembership table:
DELETE FROM PortfolioMembership WHERE PortfolioId='1172684730399265' AND UserId='1172686741877880'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the portfoolio membership. | |
PortfolioId [KEY] | String | True |
Portfolios.Id |
The portfolio the user is a member of. |
PortfolioName | String | True |
The name of the portfolio. | |
UserId [KEY] | String | True |
Users.Id |
Globally unique ID of the user. |
UserName | String | True |
The users name. | |
ResourceType | String | True |
The resource type of this resource. | |
WorkspaceId | String | True |
Workspaces.Id |
Globally unique ID of the workspace. This column is a Pseudocolmn and its used in SELECT Query. |
To Create, update, delete, and query from Portfolios table.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The [WorkspaceId AND OwnerId] OR Id is required to make a request and rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Portfolios WHERE WorkspaceId = '1172686716695308' AND OwnerId = '1172686741877880' SELECT * FROM Portfolios WHERE Id = '1172684730399265'
WorkspaceId is a mandatory column for inserting into Portfolios table. For example:
INSERT INTO Portfolios (Name, Color, WorkspaceId) VALUES ('Test', 'dark-pink','1172686716695308'
Following is an example of how to update a Portfolios table:
"UPDATE Portfolios SET Name = 'IT-Test' WHERE Id = '1173026173301164'
Following is an example of how to delete from Portfolios table:
DELETE FROM Portfolios WHERE Id = '1172684730399265'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the portfolio. | |
Name | String | False |
Name of the portfolio. | |
Color | String | False |
Color of the portfolio. The allowed values are dark-pink, dark-green, dark-blue, dark-red, dark-teal, dark-brown, dark-orange, dark-purple, dark-warm-gray, light-pink, light-green, light-blue, light-red, light-teal, light-brown, light-orange, light-purple, light-warm-gray. | |
CreatedAt | Datetime | True |
The time at which this portfolio was created. | |
CreatorId | String | True |
Globally unique ID of the user created this portfolio. | |
CreatorName | String | True |
The users name. | |
Members | String | False |
Array of users who are members of this portfolio. | |
OwnerId | String | False |
Users.Id |
Globally unique ID of the Owner. |
OwnerName | String | True |
The Owners Name. | |
ResourceType | String | True |
The base type of this resource. | |
WorkspaceId | String | False |
Workspaces.Id |
The workspace or organization that the portfolio belongs to. |
WorkspaceName | String | True |
Name of the workspace. |
To Create, Delete and Query memberships in the Project.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM ProjectMembership WHERE Id = '1127092449876445' SELECT * FROM ProjectMembership WHERE ProjectId = '1127092449876444'
UserId and ProjectId is a mandatory column for inserting into ProjectMembership table. For example:
INSERT INTO ProjectMembership (UserId, ProjectId) VALUES ('1161963899354167','1128092964672848')
Following is an example of how to delete from ProjectMembership table:
DELETE FROM ProjectMembership WHERE UserId = '1161963899354167' AND ProjectId = '1128092964672848'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the project membership. | |
ProjectId [KEY] | String | False |
Projects.Id |
The project the user is a member of. |
WriteAccess | String | True |
Whether the user has full access to the project or has comment-only access. | |
UserId [KEY] | String | False |
Users.Id |
The user in the membership. |
ResourceType | String | True |
The resource type of this resource. |
To Create, Update, Delete and Query the Projects table.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM projects WHERE workspaceId = '1126938837961830' SELECT * FROM projects WHERE Id = '1128092864672888' SELECT * FROM projects WHERE TaskId = '1130092964672468'
WorkspaceId or TeamId is a mandatory column for inserting into Projects table. For example:
INSERT INTO Projects (Name, Color, StartOn, WorkspaceId, DueOn, public, UserId) values ('ProjectName', 'dark-pink', '2020-03-01', '1126938837961830', '2020-04-30', false, '1130062547672468')
Following is an example of how to update a Projects table:
UPDATE Projects SET TeamId = '1129514033997890' WHERE Id = '1128092864672888'
Following is an example of how to delete from Projects table:
DELETE FROM Projects WHERE Id = '1128092864672888'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the project. | |
Name | String | False |
Name of the project. This is generally a short sentence fragment that fits on a line in the UI for maximum readability. However, it can be longer. | |
Color | String | False |
Color of the project. Must be either null or one of: dark-pink, dark-green, dark-blue, dark-red, dark-teal, dark-brown, dark-orange, dark-purple, dark-warm-gray, light-pink, light-green, light-blue, light-red, light-teal, light-yellow, light-orange, light-purple, light-warm-gray. The allowed values are dark-pink, dark-green, dark-blue, dark-red, dark-teal, dark-brown, dark-orange, dark-purple, dark-warm-gray, light-pink, light-green, light-blue, light-red, light-teal, light-brown, light-orange, light-purple, light-warm-gray, green, yellow, red. | |
CreatedAt | Datetime | True |
The time at which this project was created. | |
ModifiedAt | Datetime | True |
The time at which this project was last modified. | |
StartOn | Date | False |
The day on which work for this project begins, or null if the project has no start date. This takes a date with YYYY-MM-DD format. Note: due_on must be present in the request when setting or unsetting the start_on parameter. | |
DueOn | Date | False |
The day on which this project is due. This takes a date with format YYYY-MM-DD. | |
DefaultView | String | False |
The default view of a project. The allowed values are list, board, calendar, timeline. | |
Followers | String | False |
Followers are a subset of members who receive all notifications for a project. | |
Archived | Boolean | False |
True if the project is archived, false if not. Archived projects do not show in the UI by default and may be treated differently for queries. | |
UserId | String | False |
Users.Id |
The current owner of the project. |
TeamId | String | False |
Teams.Id |
The team that this project is shared with. This field only exists for projects in organizations. |
WorkspaceId | String | True |
Workspaces.Id |
The workspace or organization this project is associated with. Once created, projects cannot be moved to a different workspace. This attribute can only be specified at creation time. |
Public | Boolean | False |
True if the project is public to the organization. If false, do not share this project with other users in this organization without explicitly checking to see if they have access. | |
Notes | String | False |
More detailed, free-form textual information associated with the project. | |
HTMLNotes | String | False |
The notes of the project with formatting as HTML. | |
IsTemplate | Boolean | False |
Determines if the project is a template. | |
Layout | String | True |
The layout (board or list view) of a project. | |
Members | String | True |
Array of users who are members of this project. | |
SectionMigrationStatus | String | True |
The section migration status of this project. | |
TaskId | String | True |
Globally unique ID of the Task. |
To Create, Delete and Query from ProjectStatuses table. A project status is an update on the progress of a particular project, and is sent out to all project followers when created.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM ProjectStatuses WHERE Id = '1127092449876445' SELECT * FROM ProjectStatuses WHERE ProjectId = '1127092449876444'
ProjectId is a mandatory column for inserting into ProjectStatuses table. For example:
INSERT INTO projectstatuses (Color, Title, Text, ProjectId) VALUES ('red', 'Status1', 'StatusNotes','1127092449876444')
Following is an example of how to delete from ProjectStatuses table:
DELETE FROM ProjectStatuses WHERE Id = '1127092449876445'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the project status update. | |
Color | String | True |
The color associated with the status update. The allowed values are green, yellow, red. | |
Title | String | True |
The title of the project status update. | |
Text | String | True |
The text content of the status update. | |
CreatedAt | Datetime | True |
The time at which the status update was created. | |
CreatedBy | String | True |
The creator of the status update. | |
ProjectId | String | True |
Projects.Id |
Globally unique ID of the project. |
ResourceType | String | True |
The resource type of this resource. The value for this resource is always project_status. | |
HTMLText | String | True |
The notes of the project with formatting as HTML. |
To Create, Update, Delete, and Query from Sections table. A section is a subdivision of a project that groups tasks together.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Sections WHERE Id = '1127092449876457' SELECT * FROM Sections WHERE ProjectId = '1128092964672848'
ProjectId is a mandatory column for inserting into Sections table. For example:
INSERT INTO Sections (Name, ProjectId) VALUES ('SectionName', '1128092964672848')
Following is an example of how to update a Sections table:
UPDATE Sections SET Name='IT-Pending' WHERE Id='1127092449876457'
Following is an example of how to delete from Sections table:
DELETE FROM Sections WHERE Id = '1127092449876457'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the section. | |
Name | String | False |
The name of the section. | |
CreatedAt | Datetime | True |
The time at which the section was created. | |
ResourceType | String | True |
The resource type of this resource. | |
ProjectId | String | False |
Projects.Id |
The section under the project. |
To Create, Update, Delete and Query from stories table. A story represents an activity associated with an object in the Asana system. Stories are generated by the system whenever users take actions such as creating or assigning tasks, or moving tasks between projects.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The TaskId or Id is required to make a request and rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Stories WHERE Id = '1126938691750986' SELECT * FROM Stories WHERE TaskId = '1129514033997892'
TaskId is a mandatory column for inserting into Stories table. For example:
INSERT INTO Stories (Text, TaskId, IsPinned) VALUES ('InProgress', '1129514033997892', false)
Following is an example of how to update a Stories table:
UPDATE Stories SET Text = 'story line' WHERE Id = '1126938691750986'
Following is an example of how to delete from Stories table:
DELETE FROM Stories WHERE Id = '1126938691750986'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the story. | |
Text | String | False |
Formatted text for the story or comment. | |
CreatedAt | Datetime | True |
The time at which this story was created. | |
creatorId | String | True |
The user who created the story. | |
creatorName | String | False |
Users.Name |
The user who created the story. |
Source | String | True |
The component of the Asana product the user used to create the story. | |
TaskId | String | False |
Tasks.Id |
The story under the task. |
Liked | Boolean | True |
True if the story is liked by the authorized user, false if not. | |
IsPinned | Boolean | False |
This field is only present on comment and attachment stories. | |
IsEdited | Boolean | True |
Whether the text of the story has been edited after creation. | |
ResourceType | String | True |
The resource type of this resource. | |
ResourceSubType | String | True |
The type of story. This provides fine-grained information about what triggered the story creation. | |
HtmlText | String | True |
HTML formatted text for a comment. | |
DuplicateTaskOf | String | True |
The task is the basic object around which many operations in Asana are centered. | |
DependencyTaskId | String | True |
The task is the basic object around which many operations in Asana are centered. | |
NumberofLikes | Integer | True |
The number of users who have liked this story. | |
Likes | String | True |
Array of likes for users who have liked this story. |
To Create, update, delete, and query from SubTasks table.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following query is processed on server side and it is a required filter:
SELECT * FROM SubTasks WHERE ParentTaskId = '1127092449876457'
A simple SELECT query will only return the first level of subtasks.
SELECT * FROM SubTasks
There may be up to five levels of subtasks below a task. (Note, Asana does not recommend using sub-subtasks).
If additional levels of subtasks are needed, a subquery can be used:
SELECT * FROM SubTasks WHERE ParentTaskId IN (SELECT Id FROM SubTasks)
When executing a query without a ParentTaskId filter, due to the Asana API design, subtasks are only retrieved on a per task basis. The Cloud will first query the
workspace to retrieve a list of projects. A separate request will then be made for each project to retrieve all the applicable tasks. Another request will be made for
each task to retrieve any subtasks associated with the task. In theory, this is similar to executing the following query:
SELECT * FROM SubTasks WHERE ParentTaskId IN (SELECT Id FROM Tasks WHERE ProjectId IN (SELECT Id FROM Projects))Due to the number of required requests, performance may be impacted.
ParentTaskId is a mandatory column for inserting into Projects table. For example:
INSERT INTO SubTasks (ParentTaskId, Name, Assignee, AssigneeStatus, startOn, DueOn, Completed, ProjectId, Notes, ApprovalStatus, Followers) VALUES ('1167713816822372', 'subtask1', '1167715005778471', 'later', '2020-03-25', '2020-04-01',false,1167713816822364, 'SubTask Notes', 'changes_requested', '1167715005778471')
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the Subtask. | |
ParentTaskId | String | True |
Globally unique ID of the task. | |
Name | String | False |
Name of the Subtask. | |
Assignee | String | False |
User to which this subtask is assigned. | |
AssigneeStatus | String | False |
Scheduling status of this subtask for the user it is assigned to. The allowed values are today, upcoming, later, new, inbox. | |
CreatedAt | Datetime | True |
The time at which this subtask was created. | |
ModifiedAt | Datetime | True |
The time at which this subtask was last modified. | |
startOn | Date | False |
The day on which work begins for the task , or null if the task has no start date. This takes a date with YYYY-MM-DD format. | |
DueAt | Datetime | False |
Date and time on which this subtask is due, or null if the subtask has no due time. | |
DueOn | Date | False |
Date on which this task is due, or null if the task has no due date. This takes a date with YYYY-MM-DD format. | |
Completed | Boolean | False |
True if the subtask is currently marked complete, false if not. | |
CompletedAt | Datetime | True |
The time at which this subtask was completed, or null if the subtask is incomplete. | |
completed_by | String | True |
The user who completed this task. | |
ProjectId | String | False |
Projects.Id |
Globally unique ID of the Project. |
WorkspaceId | String | False |
Workspaces.Id |
Globally unique ID of the Workspace. |
Notes | String | False |
More detailed, free-form textual information associated with the subtask. | |
ApprovalStatus | String | False |
Reflects the approval status of this task. The allowed values are pending, approved, rejected, changes_requested. | |
ResourceSubType | String | False |
The subtype of this resource. Different subtypes retain many of the same fields and behavior, but may render differently in Asana or represent resources with different semantic meaning. The allowed values are default_task, milestone, section, approval. | |
HtmlNotes | String | False |
The notes of the text with formatting as HTML. | |
Dependencies | String | True |
Array of resources referencing tasks that this task depends on. | |
Memberships | String | True |
Array of projects this task is associated with and the section it is in. | |
Dependents | String | True |
Array of resources referencing tasks that depend on this task. | |
Liked | Boolean | False |
True if the task is liked by the authorized user, false if not. | |
NumberofLikes | Integer | True |
The number of users who have liked this Task. | |
LikedBy | String | True |
Array of likes for users who have liked this task. | |
ResourceType | String | True |
The base type of this resource. | |
IsRenderedAsSeparator | Boolean | True |
In some contexts tasks can be rendered as a visual separator. | |
Followers | String | False |
Array of users following this task. | |
Tags | String | False |
Array of tags associated with this task. |
To Create, Update and Query from Tags table. A tag is a label that can be attached to any task in Asana. It exists in a single workspace.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Tags WHERE Id = '1129517083601713' SELECT * FROM Tags WHERE WorkspaceId = '1126938837961830' SELECT * FROM Tags WHERE TaskId = '1128092964672854'
Workspaceid is a mandatory column for inserting into Tags table. For example:
INSERT INTO Tags (Name, Color, WorkspaceId, Notes) VALUES ('TestTag', 'dark-blue', '1126938837961830','sample notes')
Following is an example of how to update a Tags table:
UPDATE Tags SET Name='IT-1' WHERE Id='1158271967831255'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the tag. | |
Name | String | True |
Name of the tag. | |
CreatedAt | Datetime | True |
The time at which this tag was created. | |
Color | String | True |
Color of the tag. The allowed values are dark-pink, dark-green, dark-blue, dark-red, dark-teal, dark-brown, dark-orange, dark-purple, dark-warm-gray, light-pink, light-green, light-blue, light-red, light-teal, light-brown, light-orange, light-purple, light-warm-gray. | |
Notes | String | False |
Notes of the tag. | |
Followers | String | True |
Followers for the tag. | |
WorkspaceId | String | True |
Workspaces.Id |
The workspace or organization this tag is associated with. |
TaskId | String | True |
Tasks.Id |
The task this tag is mapped with. |
To Create, Update, Delete and Query from Tasks table.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Tasks WHERE Id = '1127092449876457' SELECT * FROM Tasks WHERE ProjectId = '1128092964672848' SELECT * FROM Tasks WHERE Assignee = '1126938691750986' AND WorkspaceId = '1126938837961830' SELECT * FROM Tasks WHERE Assignee = '1126938691750986' SELECT * FROM tasks WHERE TagId = '1129517083601713' SELECT * FROM tasks WHERE SectionId = '1127092449876457' SELECT * FROM tasks WHERE UserTaskListId = '1126938837961837'
When executing a query without one of the above filters, due to the Asana API design, tasks must be retrieved per project. The Cloud will first query the
workspace to retrieve a list of projects. A separate request will then be made for each project to retrieve all the applicable tasks. In theory, this is similar
to executing the following query:
SELECT * FROM Tasks WHERE ProjectId IN (SELECT Id FROM Projects)Due to the number of required requests, performance may be impacted. Note, tasks may also be orphaned and not belong to a project. The Cloud will not be able to retrieve orphaned tasks.
ProjectId is a mandatory column for inserting into Tasks table. For example:
INSERT INTO Tasks (Name, Assignee, AssigneeStatus, startOn, DueOn, Completed, ProjectId, Notes, ApprovalStatus, Followers) VALUES ('Task1', '1167715005778471', 'later', '2020-03-25', '2020-04-01',false,1167713816822364, 'TaskNotes', 'changes_requested', '1167715005778471')
Following is an example of how to update a Tasks table:
UPDATE Tasks SET Browser='ie' WHERE Id = '1167713816822371'
Following is an example of how to delete from Tasks table:
DELETE FROM Tasks WHERE Id = '1167713816822371'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the task. | |
Name | String | False |
Name of the task. | |
Assignee | String | False |
User to which this task is assigned. | |
AssigneeStatus | String | False |
Scheduling status of this task for the user it is assigned to. The allowed values are today, upcoming, later, new, inbox. | |
CreatedAt | Datetime | True |
The time at which this task was created. | |
ModifiedAt | Datetime | True |
The time at which this task was last modified. | |
startOn | Date | False |
Date and time on which this task is due, or null if the task has no due time. | |
DueAt | Datetime | False |
Date and time on which this task is due, or null if the task has no due time. | |
DueOn | Date | False |
Date on which this task is due, or null if the task has no due date. This takes a date with YYYY-MM-DD format. | |
Completed | Boolean | False |
True if the task is currently marked complete, false if not. | |
CompletedAt | Datetime | True |
The time at which this task was completed, or null if the task is incomplete. | |
CompletedBy | String | True |
The user who completed this task. | |
ProjectId | String | False |
Projects.Id |
Projectid of this task is associated with. |
Projects | String | False |
Projects of this task is associated with. | |
WorkspaceId | String | False |
Workspaces.Id |
Globally unique ID of the Workspace. |
Notes | String | False |
More detailed, free-form textual information associated with the task. | |
NumberofSubTasks | Integer | True |
The number of subtasks on this task. | |
ApprovalStatus | String | False |
Reflects the approval status of this task. The allowed values are pending, approved, rejected, changes_requested. | |
ResourceSubType | String | False |
The subtype of this resource. Different subtypes retain many of the same fields and behavior, but may render differently in Asana or represent resources with different semantic meaning. The allowed values are default_task, milestone, section, approval. | |
HtmlNotes | String | False |
The notes of the text with formatting as HTML. | |
Memberships | String | True |
Array of projects this task is associated with and the section it is in. | |
Dependencies | String | True |
Array of resources referencing tasks that this task depends on. | |
Dependents | String | True |
Array of resources referencing tasks that depend on this task. | |
Liked | Boolean | True |
True if the task is liked by the authorized user, false if not. | |
NumberofLikes | Integer | True |
The number of users who have liked this Task. | |
LikedBy | String | True |
Array of likes for users who have liked this task. | |
ResourceType | String | True |
The base type of this resource. | |
IsRenderedAsSeparator | Boolean | True |
In some contexts tasks can be rendered as a visual separator. | |
Followers | String | True |
Array of users following this task. | |
Tags | String | False |
Array of tags associated with this task. | |
SectionId | String | True |
Sections.Id |
PseudoColumn: Globally unique ID of the section. |
UserTaskListId | String | True |
WorkspaceMembership.UserTaskListId |
PseudoColumn: A user task list represents the tasks assigned to a particular user. |
TagId | String | True |
Tags.Id |
PseudoColumn: Globally unique ID of the tag. |
To represents a users connection to a team.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM TeamMembership WHERE UserId = '1126938691750986' AND WorkspaceId = '1126938837961830' SELECT * FROM TeamMembership WHERE TeamId = '1126938837961832' SELECT * FROM TeamMembership WHERE Id = '1126938837961832'
UserId and TeamId is a mandatory column for inserting into TeamMembership table. For example:
INSERT INTO TeamMembership (UserId, TeamId) VALUES ('1161963899354167','1126938837961832')
Following is an example of how to delete from TeamMembership table:
DELETE FROM TeamMembership WHERE UserId = '1161963899354167' AND TeamId = '1126938837961832'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique identifier of the resource, as a string. | |
userId | String | True |
Globally unique ID of the user. | |
userName | String | True |
The users name. | |
TeamId | String | True |
Globally unique ID of the team. | |
TeamName | String | True |
The name of the team. | |
IsGuest | Boolean | True |
Describes if the user is a guest in the team. | |
ResourceType | String | True |
The base type of this resource. | |
WorkspaceId | String | True |
Globally unique ID of the workspace. |
A team is used to group related projects and people together within an organization. Each project in an organization is associated with a team.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Teams WHERE Id = '1126938837961832' SELECT * FROM Teams WHERE WorkspaceId = '1126938837961830' SELECT * FROM Teams WHERE UserId = '1126938691750986' AND workspaceid = '1126938837961830'
INSERT INTO Teams (Name,Description,HTMLDescrption,WorkspaceId) Values ('Salessssk','sales developers should be members of this team.','<body> <em>All</em> developers should be members of this team.</body>','1126938837961830')
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the team. | |
Name | String | True |
The name of the team. | |
Description | String | True |
The description of the team. | |
WorkspaceId | String | True |
Workspaces.Id |
The workspace or organization this team is associated with. |
HTMLDescrption | String | True |
The description of the team with formatting as HTML. | |
ResourceType | String | True |
The resource type of this resource. | |
UserId | String | True |
Users.Id |
Globally unique ID of the user. |
To Create, Delete and Query memberships in the Workspace.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM WorkspaceMembership WHERE WorkspaceId = '1126938837961830' SELECT * FROM WorkspaceMembership WHERE UserId = '1126938691750986' SELECT * FROM WorkspaceMembership WHERE Id = '1126938837961834'
UserId and WorkspaceId is a mandatory column for inserting into WorkspaceMembership table. For example:
INSERT INTO WorkspaceMembership (UserId, WorkspaceId) VALUES ('1161963899354167','1126938837961830')
Following is an example of how to delete from WorkspaceMembership table:
DELETE FROM WorkspaceMembership WHERE UserId = '1161963899354167' AND WorkspaceId = '1126938837961830'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the membership. | |
userId [KEY] | String | True |
Globally unique ID of the user. | |
userName | String | True |
The user`s name. | |
WorkspaceId [KEY] | String | True |
Globally unique ID of the workspace. | |
WorkspaceName | String | True |
The Workspace name. | |
IsActive | Boolean | True |
Reflects if this user still a member of the workspace. | |
IsAdmin | Boolean | True |
Reflects if this user is an admin of the workspace. | |
IsGuest | Boolean | True |
Reflects if this user is a guest of the workspace. | |
UserTaskListId | String | True |
A user task list represents the tasks assigned to a particular user. | |
ResourceType | String | True |
The base type of this resource. |
To Update and Query from Workspaces table. A workspace is the highest-level organizational unit in Asana. All projects and tasks have an associated workspace.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Workspaces WHERE Id = '1126938837961835' SELECT * FROM Workspaces WHERE UserId = '1126938691750986'
Following is an example of how to update a Workspaces table:
UPDATE Workspaces SET Name='IT-Eng' WHERE Id='1126938837961835'
Name | Type | ReadOnly | References | Description |
Id [KEY] | String | True |
Globally unique ID of the workspace. | |
Name | String | False |
The name of the workspace. | |
ResourceType | String | True |
The resource type of this resource. | |
IsOrganization | Boolean | True |
Whether the workspace is an organization. | |
EmailDomains | String | True |
Whether the workspace is an organization. | |
UserId | String | True |
Users.Id |
Globally unique ID of the user. |
Views are composed of columns and pseudo columns. Views are similar to tables in the way that data is represented; however, views do not support updates. Entities that are represented as views are typically read-only entities. Often, a stored procedure is available to update the data if such functionality is applicable to the data source.
Queries can be executed against a view as if it were a normal table, and the data that comes back is similar in that regard.
Dynamic views, such as queries exposed as views, and views for looking up specific combinations of project_team work items are supported.
Name | Description |
CustomFields | To view the Custom Fields in the project. |
Events | To view the events in projects and tasks. |
ProjectFollowers | To view the Project follower details. |
ProjectTemplates | TO get ProjectTemplates in the Team or workspace. |
TaskStatuses | Get task count of a project. |
Users | To view the users details. |
UserTaskList | Generated schema file. |
To view the Custom Fields in the project.
The Cloud uses the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side in the Cloud.
For example, the following query is processed server side:
SELECT * FROM CustomFields WHERE ProjectId = '1126938691750986'
Name | Type | References | Description |
Id | String | Globally unique identifier of the resource. | |
Name | String | The name of the custom field. | |
Description | String | The description of the custom field. | |
Type | String | The type of the custom field. It must be one of the given values. | |
ProjectId | String | Globally unique Id of the project. | |
ProjectName | String | Name of the project. | |
IsImportant | Boolean | Name of the project. | |
Format | String | The format of the custom field. | |
TextValue | String | The value of a text custom field. | |
NumberValue | Double | The value of a number custom field. | |
Precision | Integer | Only relevant for custom fields of type 'Number'. This field specifies the number of digits after the decimal to round to. | |
CurrencyCode | String | The currency code for this custom field. The value is null if the format is not currency. | |
EnumOptions | String | Array of projects this task is associated with and the section it is in. | |
CreatedBy | String | Globally unique user identifier. | |
CreatedByName | String | The user's name. | |
IsGlobaltoWorkspace | Boolean | A flag that specifies whether this custom field is available to every container in the workspace. | |
HasNotificationsEnabled | Boolean | A flag that specifies whether a follower of a task with this field should receive inbox notifications about changes in this field. |
To view the events in projects and tasks.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The resource id will be either Project or Task Id. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Events WHERE ResourceId = '1128092964672854'
Name | Type | References | Description |
ResourceId [KEY] | String | The resource GID for the events were requested for. | |
ResourceType | String | The resource type for the events were requested for. | |
ResourceSubType | String | The resource sub type for the events were requested for. | |
ResourceName | String | The resource name for the events were requested for. | |
Parent | String | For added/removed events, the parent that resource was added to or removed from. null for other event types. | |
CreatedAt | Datetime | The timestamp when the event occurred. | |
UserId | String | The event may be triggered by a different user GID than the subscriber. | |
UserFullname | String | The event may be triggered by a different user name than the subscriber. | |
Action | String | The type of action taken that triggered the event. |
To view the Project follower details.
Name | Type | References | Description |
ProjectId | String |
Projects.Id | Globally unique ID of the Project. |
UserId | String | Globally unique ID of the user. | |
UserName | String | The user`s name. | |
ResourceType | String | The resource type of this resource. | |
WorkspaceId | String |
Workspaces.Id | The workspace this Project is associated with. |
TO get ProjectTemplates in the Team or workspace.
Name | Type | References | Description |
Id [KEY] | String | Globally unique identifier of the resource, as a string. | |
Color | String | Color of the project template. | |
Description | String | Free-form textual information associated with the project template. | |
Html_description | String | The description of the project template with formatting as HTML. | |
Name | String | Name of the project template. | |
OwnerId | String | A user object. Globally unique identifier of the resource, as a string. | |
OwnerName | String | A user object. The base type of this resource. | |
OwnerResourceType | String | A user object. Read-only except when same user as requester. The name of the User. | |
IsPublic | Boolean | True if the project template is public to its team. | |
RequestedDates | String | Array of date variables in this project template. Calendar dates must be provided for these variables when instantiating a project. | |
ResourceType | String | The base type of this resource. | |
TeamId | String |
Teams.Id | A team is used to group related projects and people together within an organization. Globally unique identifier of the resource, as a string. |
TeamName | String | A team is used to group related projects and people together within an organization. The name of the team. | |
TeamResourceType | String | A team is used to group related projects and people together within an organization. The base type of this resource. |
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 | |
WorkspaceId | String | The workspace Id to filter results on. |
Get task count of a project.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM TaskStatuses WHERE ProjectId = '1136437449978157'
Name | Type | References | Description |
ProjectId | String |
Projects.Id | Globally unique ID of the project. |
NumberofTasks | Integer | The number of tasks in a project. | |
CompletedTasks | Integer | The number of completed tasks in a project. | |
IncompleteTasks | Integer | The number of incomplete tasks in a project. | |
NumberofMilestones | Integer | The number of milestones in a project. | |
CompletedMilestones | Integer | The number of completed milestones in a project. | |
InCompleteMilestones | Integer | The number of incomplete milestones in a project. |
To view the users details.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM Users WHERE Id = '1126938691750986' SELECT * FROM Users WHERE WorkspaceId = '1126938837961835' SELECT * FROM Users WHERE TeamId = '1129514033997892'
Name | Type | References | Description |
Id [KEY] | String | Globally unique ID of the user. | |
Name | String | The user`s name. | |
String | The user`s email address. | ||
ResourceType | String | The resource type of this resource. | |
WorkspaceId | String |
Workspaces.Id | The User access in workspaces. |
TeamId | String |
Teams.Id | Globally unique ID of the team. |
Generated schema file.
The Cloud will use the Asana API to process WHERE clause conditions built with the following column and operator. The [UserId and workspaceId] or Id is required to make a request and the rest of the filter is executed client side within the Cloud.
For example, the following queries are processed server side:
SELECT * FROM UserTaskList WHERE Id = '1126938837961837' SELECT * FROM UserTaskList WHERE UserId = '1126938691750986' AND workspaceId = '1126938837961830'
Name | Type | References | Description |
Id [KEY] | String |
WorkspaceMembership.UserTaskListId | Globally unique ID of the user task list. |
Name | String | The name of the user task list. | |
UserId | String |
Users.Id | The owner of the user task list. |
workspaceId | String |
Workspaces.Id | The workspace in which the user task list is located. |
ResourceType | String | The resource type of this resource. |
Stored procedures are function-like interfaces that extend the functionality of the Cloud beyond simple SELECT/INSERT/UPDATE/DELETE operations with Asana.
Stored procedures accept a list of parameters, perform their intended function, and then return, if applicable, any relevant response data from Asana, along with an indication of whether the procedure succeeded or failed.
Name | Description |
AddDependenciesToTask | To set of tasks as dependencies of this task, if they are not already dependencies. A task can have at most 15 dependencies. |
AddDependentsToTask | To Set or Unlink dependents to the task. |
AddFollowers | To add followers to the tasks or projects. |
AddProjectToTask | Add a project to a task. |
AddTagsToTask | To Set or Unlink dependents to the task. |
AddTaskToSection | Add a task to a specific, existing section. This will remove the task from other sections of the project. |
DuplicateProject | To create a duplicate copy of the project. |
DuplicateTask | To Set or Unlink dependencies to the task. |
MoveSectionsinProject | To reorder the section in the project. |
RemoveDependenciesFromTask | To Set or Unlink dependencies to the task. |
RemoveDependentsFromTask | To Set or Unlink dependents to the task. |
RemoveFollowers | To remove followers from the tasks or projects. |
RemoveProjectsFromTask | Remove a project from a task. |
RemoveTagsFromTask | To Set or Unlink dependents to the task. |
SetParentofTask | To Set the parent of a task. |
To set of tasks as dependencies of this task, if they are not already dependencies. A task can have at most 15 dependencies.
Name | Type | Required | Description |
TaskId | String | True | The Tasks Id to operate on. |
Dependencies | String | True | Task ids to add dependencies. For more than One task Id please separate with comma(,). |
Name | Type | Description |
Status | String | The status of the operation. |
To Set or Unlink dependents to the task.
Name | Type | Required | Description |
TaskId | String | True | The Tasks Id to operate on. |
DependentTaskId | String | True | Task ids to add or remove as dependents. For more than One task Id please separate with comma(,). |
Name | Type | Description |
Status | String | The status of the operation. |
To add followers to the tasks or projects.
Name | Type | Required | Description |
Id | String | True | The Tasks Id or Project Id to operate on. |
User | String | True | Users.Id OR Users.EMail to Add. |
TableName | String | True | To add the followers in.
The allowed values are projects, tasks. |
Name | Type | Description |
Status | String | The status of the operation. |
Add a project to a task.
Name | Type | Required | Description |
TaskId | String | True | The Tasks Id to operate on. |
ProjectId | String | True | The project Id to add the task. |
SectionId | String | False | A section Id in the project to insert the task into. The task will be inserted at the bottom of the section. |
AddAfter | String | False | A task Id in the project to insert the task after, or null to insert at the beginning of the list. |
AddBefore | String | False | A task Id in the project to insert the task before, or null to insert at the end of the list. |
Name | Type | Description |
Status | String | The status of the operation. |
To Set or Unlink dependents to the task.
Name | Type | Required | Description |
TaskId | String | True | The Tasks Id to operate on. |
TagId | String | True | Tags Id to add in the task. |
Name | Type | Description |
Status | String | The status of the operation. |
Add a task to a specific, existing section. This will remove the task from other sections of the project.
Name | Type | Required | Description |
SectionId | String | True | A section Id in the project to move the task into. |
TaskId | String | True | The task Id to add to this section. |
AddAfter | String | False | An existing task id within this section before which the added task should be inserted. Cannot be provided together with insert_after. |
Status | String | False | The status of the operation. |
To Download an Attachment.
Name | Type | Required | Description |
AttachmentId | String | False | Attachment Id to download. |
TaskId | String | False | Task Id to download all the attachments in the Task. |
DownloadLocation | String | False | Download location. |
Encoding | String | False | The FileData input encoding type.
The allowed values are NONE, BASE64. The default value is BASE64. |
Name | Type | Description |
Status | String | The status of the operation. |
FileData | String | The file data output. |
To create a duplicate copy of the project.
Name | Type | Required | Description |
ProjectId | String | True | Globally unique identifier for the project. |
NewProjectName | String | True | The name of the new project. |
Include | String | True | The fields that will be duplicated to the new task. The accepted values are members, notes, task_notes, task_assignee, task_subtasks, task_attachments, task_dates, task_dependencies, task_followers, task_tags, task_projects. For more than One values, please separate with comma(,). |
TeamId | String | False | Sets the team of the new project. If team is not defined, the new project will be in the same team as the the original project. |
DueOn | Date | False | Sets the last due date in the duplicated project to the given date. The rest of the due dates will be offset by the same amount as the due dates in the original project. This takes a date with format YYYY-MM-DD. |
StartOn | Date | False | Sets the first start date in the duplicated project to the given date. The rest of the start dates will be offset by the same amount as the start dates in the original project. This takes a date with format YYYY-MM-DD. |
SkipWeekends | Boolean | False | Determines if the auto-shifted dates should skip weekends. |
Name | Type | Description |
Status | String | The status of the operation. |
To Set or Unlink dependencies to the task.
Name | Type | Required | Description |
TaskId | String | True | The Task Id to operate on. |
NewTaskName | String | True | The name of the new task. |
Include | String | True | The fields that will be duplicated to the new task. The accepted values are notes,assignee,subtasks,attachments,tags,followers,projects,dates,dependencies,parent. For more than One values please separate with comma(,). |
Name | Type | Description |
Status | String | The status of the operation. |
Gets an authentication token from Asana.
Name | Type | Required | Description |
AuthMode | String | False | The type of authentication mode to use. Select App for getting authentication tokens via a desktop app. Select Web for getting authentication tokens via a Web app.
The allowed values are APP, WEB. The default value is APP. |
CallbackUrl | String | False | The URL the user will be redirected to after authorizing your application. This value must match the Redirect URL you have specified in the Asana app settings. Only needed when the Authmode parameter is Web. |
Verifier | String | False | The verifier returned from Asana after the user has authorized your app to have access to their data. This value will be returned as a parameter to the callback URL. |
State | String | False | Encodes state of the app, which will be returned verbatim in the response and can be used to match the response up to a given request. |
Name | Type | Description |
OAuthAccessToken | String | The access token used for communication with Asana. |
OAuthRefreshToken | String | The OAuth refresh token. This is the same as the access token in the case of Asana. |
ExpiresIn | String | The remaining lifetime on the access token. A -1 denotes that it will not expire. |
Gets the authorization URL that must be opened separately by the user to grant access to your application. Only needed when developing Web apps. You will request the OAuthAccessToken from this URL.
Name | Type | Required | Description |
CallbackUrl | String | False | The URL the user will be redirected to after authorizing your application. This value must match the Redirect URL in the Asana app settings. |
State | String | False | Encodes state of the app, which will be returned verbatim in the response and can be used to match the response up to a given request. |
Name | Type | Description |
URL | String | The authorization URL, entered into a Web browser to obtain the verifier token and authorize your app. |
To reorder the section in the project.
Name | Type | Required | Description |
ProjectId | String | True | The project in which to reorder the given section. |
SectionId | String | True | The section to reorder. |
BeforeSection | String | False | Insert the given section immediately before the section specified by this parameter. |
AfterSection | String | False | Insert the given section immediately after the section specified by this parameter. |
Name | Type | Description |
Status | String | The status of the operation. |
Refreshes the OAuth access token used for authentication with Asana.
Name | Type | Required | Description |
OAuthRefreshToken | String | True | Set this to the token value that expired. |
Name | Type | Description |
OAuthAccessToken | String | The authentication token returned from Asana. This can be used in subsequent calls to other operations for this particular service. |
OAuthRefreshToken | String | This is the same as the access token. |
ExpiresIn | String | The remaining lifetime on the access token. |
To Set or Unlink dependencies to the task.
Name | Type | Required | Description |
TaskId | String | True | The Tasks Id to operate on. |
DependentTaskId | String | True | Task ids to add or remove as dependents. For more than One task Id please separate with comma(,). |
Name | Type | Description |
Status | String | The status of the operation. |
To Set or Unlink dependents to the task.
Name | Type | Required | Description |
TaskId | String | True | The Tasks Id to operate on. |
DependentTaskId | String | True | Task ids to add or remove as dependents. For more than One task Id please separate with comma(,). |
Name | Type | Description |
Status | String | The status of the operation. |
To remove followers from the tasks or projects.
Name | Type | Required | Description |
Id | String | True | The Tasks Id or Project Id to operate on. |
User | String | True | Users.Id OR Users.EMail to remove. |
TableName | String | True | To remove the followers in.
The allowed values are projects, tasks. |
Name | Type | Description |
Status | String | The status of the operation. |
Remove a project from a task.
Name | Type | Required | Description |
TaskId | String | True | The Tasks Id to operate on. |
ProjectId | String | True | The project Id to add or remove the task to. |
Name | Type | Description |
Status | String | The status of the operation. |
To Set or Unlink dependents to the task.
Name | Type | Required | Description |
TaskId | String | True | The Tasks Id to operate on. |
TagId | String | True | Tags Id to remove from the task. |
Name | Type | Description |
Status | String | The status of the operation. |
To Set the parent of a task.
Name | Type | Required | Description |
TaskId | String | True | The TaskId to update. |
ParentTaskId | String | True | The new parent of the task, or null for no parent.. |
AddBefore | String | False | A subtask of the parent to insert the task after, or null to insert at the beginning of the list. |
AddAfter | String | False | A subtask of the parent to insert the task before, or null to insert at the end of the list. |
Name | Type | Description |
Status | String | The status of the operation. |
Uploads an Attachment to Asana.
Name | Type | Required | Accepts Input Streams | Description |
TaskId | String | True | False | Specify Task Id to upload the attachment. |
FilePath | String | False | False | Specify the location of the attachment to upload. |
Name | String | False | False | The title for the Attachment, including the extension. This value will be used, if Content is not null. |
Content | String | False | True | The content as InputStream to be uploaded when LocalFilePath or FolderPath is not specified. |
Name | Type | Description |
AttachmentId | String | Globally unique ID of the attachment. |
FileName | String | The name of the file. |
Status | String | The status of the operation. |
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 Asana:
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, including batch operations::
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 projects table:
SELECT ColumnName, DataTypeName FROM sys_tablecolumns WHERE TableName='projects'
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. |
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 UploadAttachment stored procedure:
SELECT * FROM sys_procedureparameters WHERE ProcedureName='UploadAttachment' 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 projects table:
SELECT * FROM sys_keycolumns WHERE IsKey='True' AND TableName='projects'
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:asana: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. The following result set indicates the SELECT functionality that the Cloud can offload to the data source or process client side. Your data source may support additional SQL syntax. 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.
Property | Description |
ProjectId | The globally unique identifier (gid) associated with your Asana Project. |
WorkspaceId | The globally unique identifier (gid) associated with your Asana Workspace. |
IncludeCustomFields | Custom fields may be added to the Tasks, SubTasks, and PortfolioItems tables. |
Property | Description |
OAuthClientId | The client Id assigned when you register your application with an OAuth authorization server. |
OAuthClientSecret | The client secret assigned when you register your application with an OAuth authorization server. |
OAuthAccessToken | The access token for connecting using OAuth. |
CallbackURL | The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings. |
OAuthVerifier | The verifier code returned from the OAuth authorization URL. |
OAuthRefreshToken | The OAuth refresh token for the corresponding OAuth access token. |
OAuthExpiresIn | The lifetime in seconds of the OAuth AccessToken. |
OAuthTokenTimestamp | The Unix epoch timestamp in milliseconds when the current Access Token was created. |
Property | Description |
SSLServerCert | The certificate to be accepted from the server when connecting using TLS/SSL. |
Property | Description |
FirewallType | The protocol used by a proxy-based firewall. |
FirewallServer | The name or IP address of a proxy-based firewall. |
FirewallPort | The TCP port for a proxy-based firewall. |
FirewallUser | The user name to use to authenticate with a proxy-based firewall. |
FirewallPassword | A password used to authenticate to a proxy-based firewall. |
Property | Description |
ProxyAutoDetect | This indicates whether to use the system proxy settings or not. This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings. |
ProxyServer | The hostname or IP address of a proxy to route HTTP traffic through. |
ProxyPort | The TCP port the ProxyServer proxy is running on. |
ProxyAuthScheme | The authentication type to use to authenticate to the ProxyServer proxy. |
ProxyUser | A user name to be used to authenticate to the ProxyServer proxy. |
ProxyPassword | A password to be used to authenticate to the ProxyServer proxy. |
ProxySSLType | The SSL type to use when connecting to the ProxyServer proxy. |
ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the ProxyServer . |
Property | Description |
Logfile | A filepath which designates the name and location of the log file. |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
LogModules | Core modules to be included in the log file. |
MaxLogFileSize | A string specifying the maximum size in bytes for a log file (for example, 10 MB). |
MaxLogFileCount | A string specifying the maximum file count of log files. |
Property | Description |
Location | A path to the directory that contains the schema files defining tables, views, and stored procedures. |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
Tables | This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC. |
Views | Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC. |
Property | Description |
AutoCache | Automatically caches the results of SELECT queries into a cache database specified by either CacheLocation or both of CacheConnection and CacheProvider . |
CacheLocation | Specifies the path to the cache when caching to a file. |
CacheTolerance | The tolerance for stale data in the cache specified in seconds when using AutoCache . |
Offline | Use offline mode to get the data from the cache instead of the live source. |
CacheMetadata | This property determines whether or not to cache the table metadata to a file store. |
Property | Description |
MaxRows | Limits the number of rows returned rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time. |
Other | These hidden properties are used only in specific use cases. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
Readonly | You can use this property to enforce read-only access to Asana from the provider. |
RTK | The runtime key used for licensing. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
UserDefinedViews | A filepath pointing to the JSON configuration file containing your custom views. |
This section provides a complete list of the Connection properties you can configure in the connection string for this provider.
Property | Description |
ProjectId | The globally unique identifier (gid) associated with your Asana Project. |
WorkspaceId | The globally unique identifier (gid) associated with your Asana Workspace. |
IncludeCustomFields | Custom fields may be added to the Tasks, SubTasks, and PortfolioItems tables. |
The globally unique identifier (gid) associated with your Asana Project.
string
""
Requests will return the data mapped under this project.
The globally unique identifier (gid) associated with your Asana Workspace.
string
""
Requests will return the projects mapped under this WorkspaceId.
Custom fields may be added to the Tasks, SubTasks, and PortfolioItems tables.
bool
false
If set to TRUE, custom fields may be added to the Tasks, SubTasks, and PortfolioItems tables. The WorkspaceId should also be specified. Custom fields are related to a specific Workspace. If no WorkspaceId is specified, the first available WorkspaceId will be used.
This section provides a complete list of the OAuth properties you can configure in the connection string for this provider.
Property | Description |
OAuthClientId | The client Id assigned when you register your application with an OAuth authorization server. |
OAuthClientSecret | The client secret assigned when you register your application with an OAuth authorization server. |
OAuthAccessToken | The access token for connecting using OAuth. |
CallbackURL | The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings. |
OAuthVerifier | The verifier code returned from the OAuth authorization URL. |
OAuthRefreshToken | The OAuth refresh token for the corresponding OAuth access token. |
OAuthExpiresIn | The lifetime in seconds of the OAuth AccessToken. |
OAuthTokenTimestamp | The Unix epoch timestamp in milliseconds when the current Access Token was created. |
The client Id assigned when you register your application with an OAuth authorization server.
string
""
As part of registering an OAuth application, you will receive the OAuthClientId value, sometimes also called a consumer key, and a client secret, the OAuthClientSecret.
The client secret assigned when you register your application with an OAuth authorization server.
string
""
As part of registering an OAuth application, you will receive the OAuthClientId, also called a consumer key. You will also receive a client secret, also called a consumer secret. Set the client secret in the OAuthClientSecret property.
The access token for connecting using OAuth.
string
""
The OAuthAccessToken property is used to connect using OAuth. The OAuthAccessToken is retrieved from the OAuth server as part of the authentication process. It has a server-dependent timeout and can be reused between requests.
The access token is used in place of your user name and password. The access token protects your credentials by keeping them on the server.
The OAuth callback URL to return to when authenticating. This value must match the callback URL you specify in your app settings.
string
"http://localhost:33333"
During the authentication process, the OAuth authorization server redirects the user to this URL. This value must match the callback URL you specify in your app settings.
The verifier code returned from the OAuth authorization URL.
string
""
The verifier code returned from the OAuth authorization URL. This can be used on systems where a browser cannot be launched such as headless systems.
See to obtain the OAuthVerifier value.
Set OAuthSettingsLocation along with OAuthVerifier. When you connect, the Cloud exchanges the OAuthVerifier for the OAuth authentication tokens and saves them, encrypted, to the specified file.
Once the OAuth settings file has been generated, you can remove OAuthVerifier from the connection properties and connect with OAuthSettingsLocation set.
To automatically refresh the OAuth token values, set OAuthSettingsLocation and additionally set InitiateOAuth to REFRESH.
The OAuth refresh token for the corresponding OAuth access token.
string
""
The OAuthRefreshToken property is used to refresh the OAuthAccessToken when using OAuth authentication.
The lifetime in seconds of the OAuth AccessToken.
string
""
Pair with OAuthTokenTimestamp to determine when the AccessToken will expire.
The Unix epoch timestamp in milliseconds when the current Access Token was created.
string
""
Pair with OAuthExpiresIn to determine when the AccessToken will expire.
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 Firewall properties you can configure in the connection string for this provider.
Property | Description |
FirewallType | The protocol used by a proxy-based firewall. |
FirewallServer | The name or IP address of a proxy-based firewall. |
FirewallPort | The TCP port for a proxy-based firewall. |
FirewallUser | The user name to use to authenticate with a proxy-based firewall. |
FirewallPassword | A password used to authenticate to a proxy-based firewall. |
The protocol used by a proxy-based firewall.
string
"NONE"
This property specifies the protocol that the Cloud will use to tunnel traffic through the FirewallServer proxy. Note that by default, the Cloud connects to the system proxy; to disable this behavior and connect to one of the following proxy types, set ProxyAutoDetect to false.
Type | Default Port | Description |
TUNNEL | 80 | When this is set, the Cloud opens a connection to Asana and traffic flows back and forth through the proxy. |
SOCKS4 | 1080 | When this is set, the Cloud sends data through the SOCKS 4 proxy specified by FirewallServer and FirewallPort and passes the FirewallUser value to the proxy, which determines if the connection request should be granted. |
SOCKS5 | 1080 | When this is set, the Cloud sends data through the SOCKS 5 proxy specified by FirewallServer and FirewallPort. If your proxy requires authentication, set FirewallUser and FirewallPassword to credentials the proxy recognizes. |
To connect to HTTP proxies, use ProxyServer and ProxyPort. To authenticate to HTTP proxies, use ProxyAuthScheme, ProxyUser, and ProxyPassword.
The name or IP address of a proxy-based firewall.
string
""
This property specifies the IP address, DNS name, or host name of a proxy allowing traversal of a firewall. The protocol is specified by FirewallType: Use FirewallServer with this property to connect through SOCKS or do tunneling. Use ProxyServer to connect to an HTTP proxy.
Note that the Cloud uses the system proxy by default. To use a different proxy, set ProxyAutoDetect to false.
The TCP port for a proxy-based firewall.
int
0
This specifies the TCP port for a proxy allowing traversal of a firewall. Use FirewallServer to specify the name or IP address. Specify the protocol with FirewallType.
The user name to use to authenticate with a proxy-based firewall.
string
""
The FirewallUser and FirewallPassword properties are used to authenticate against the proxy specified in FirewallServer and FirewallPort, following the authentication method specified in FirewallType.
A password used to authenticate to a proxy-based firewall.
string
""
This property is passed to the proxy specified by FirewallServer and FirewallPort, following the authentication method specified by FirewallType.
This section provides a complete list of the Proxy properties you can configure in the connection string for this provider.
Property | Description |
ProxyAutoDetect | This indicates whether to use the system proxy settings or not. This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings. |
ProxyServer | The hostname or IP address of a proxy to route HTTP traffic through. |
ProxyPort | The TCP port the ProxyServer proxy is running on. |
ProxyAuthScheme | The authentication type to use to authenticate to the ProxyServer proxy. |
ProxyUser | A user name to be used to authenticate to the ProxyServer proxy. |
ProxyPassword | A password to be used to authenticate to the ProxyServer proxy. |
ProxySSLType | The SSL type to use when connecting to the ProxyServer proxy. |
ProxyExceptions | A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the ProxyServer . |
This indicates whether to use the system proxy settings or not. This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings.
bool
true
This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings.
To connect to an HTTP proxy, see ProxyServer. For other proxies, such as SOCKS or tunneling, see FirewallType.
The hostname or IP address of a proxy to route HTTP traffic through.
string
""
The hostname or IP address of a proxy to route HTTP traffic through. The Cloud can use the HTTP, Windows (NTLM), or Kerberos authentication types to authenticate to an HTTP proxy.
If you need to connect through a SOCKS proxy or tunnel the connection, see FirewallType.
By default, the Cloud uses the system proxy. If you need to use another proxy, set ProxyAutoDetect to false.
The TCP port the ProxyServer proxy is running on.
int
80
The port the HTTP proxy is running on that you want to redirect HTTP traffic through. Specify the HTTP proxy in ProxyServer. For other proxy types, see FirewallType.
The authentication type to use to authenticate to the ProxyServer proxy.
string
"BASIC"
This value specifies the authentication type to use to authenticate to the HTTP proxy specified by ProxyServer and ProxyPort.
Note that the Cloud will use the system proxy settings by default, without further configuration needed; if you want to connect to another proxy, you will need to set ProxyAutoDetect to false, in addition to ProxyServer and ProxyPort. To authenticate, set ProxyAuthScheme and set ProxyUser and ProxyPassword, if needed.
The authentication type can be one of the following:
If you need to use another authentication type, such as SOCKS 5 authentication, see FirewallType.
A user name to be used to authenticate to the ProxyServer proxy.
string
""
The ProxyUser and ProxyPassword options are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
You can select one of the available authentication types in ProxyAuthScheme. If you are using HTTP authentication, set this to the user name of a user recognized by the HTTP proxy. If you are using Windows or Kerberos authentication, set this property to a user name in one of the following formats:
user@domain domain\user
A password to be used to authenticate to the ProxyServer proxy.
string
""
This property is used to authenticate to an HTTP proxy server that supports NTLM (Windows), Kerberos, or HTTP authentication. To specify the HTTP proxy, you can set ProxyServer and ProxyPort. To specify the authentication type, set ProxyAuthScheme.
If you are using HTTP authentication, additionally set ProxyUser and ProxyPassword to HTTP proxy.
If you are using NTLM authentication, set ProxyUser and ProxyPassword to your Windows password. You may also need these to complete Kerberos authentication.
For SOCKS 5 authentication or tunneling, see FirewallType.
By default, the Cloud uses the system proxy. If you want to connect to another proxy, set ProxyAutoDetect to false.
The SSL type to use when connecting to the ProxyServer proxy.
string
"AUTO"
This property determines when to use SSL for the connection to an HTTP proxy specified by ProxyServer. This value can be AUTO, ALWAYS, NEVER, or TUNNEL. The applicable values are the following:
AUTO | Default setting. If the URL is an HTTPS URL, the Cloud will use the TUNNEL option. If the URL is an HTTP URL, the component will use the NEVER option. |
ALWAYS | The connection is always SSL enabled. |
NEVER | The connection is not SSL enabled. |
TUNNEL | The connection is through a tunneling proxy. The proxy server opens a connection to the remote host and traffic flows back and forth through the proxy. |
A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the ProxyServer .
string
""
The ProxyServer is used for all addresses, except for addresses defined in this property. Use semicolons to separate entries.
Note that the Cloud uses the system proxy settings by default, without further configuration needed; if you want to explicitly configure proxy exceptions for this connection, you need to set ProxyAutoDetect = false, and configure ProxyServer and ProxyPort. To authenticate, set ProxyAuthScheme and set ProxyUser and ProxyPassword, if needed.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
Property | Description |
Logfile | A filepath which designates the name and location of the log file. |
Verbosity | The verbosity level that determines the amount of detail included in the log file. |
LogModules | Core modules to be included in the log file. |
MaxLogFileSize | A string specifying the maximum size in bytes for a log file (for example, 10 MB). |
MaxLogFileCount | A string specifying the maximum file count of log files. |
A filepath which designates the name and location of the log file.
string
""
Once this property is set, the Cloud will populate the log file as it carries out various tasks, such as when authentication is performed or queries are executed. If the specified file doesn't already exist, it will be created.
Connection strings and version information are also logged, though connection properties containing sensitive information are masked automatically.
If a relative filepath is supplied, the location of the log file will be resolved based on the path found in the Location connection property.
For more control over what is written to the log file, you can adjust the Verbosity property.
Log contents are categorized into several modules. You can show/hide individual modules using the LogModules property.
To edit the maximum size of a single logfile before a new one is created, see MaxLogFileSize.
If you would like to place a cap on the number of logfiles generated, use MaxLogFileCount.
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.
Core modules to be included in the log file.
string
""
Only the modules specified (separated by ';') will be included in the log file. By default all modules are included.
See the Logging page for an overview.
A string specifying the maximum size in bytes for a log file (for example, 10 MB).
string
"100MB"
When the limit is hit, a new log is created in the same folder with the date and time appended to the end. The default limit is 100 MB. Values lower than 100 kB will use 100 kB as the value instead.
Adjust the maximum number of logfiles generated with MaxLogFileCount.
A string specifying the maximum file count of log files.
int
-1
When the limit is hit, a new log is created in the same folder with the date and time appended to the end and the oldest log file will be deleted.
The minimum supported value is 2. A value of 0 or a negative value indicates no limit on the count.
Adjust the maximum size of the logfiles generated with MaxLogFileSize.
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
Property | Description |
Location | A path to the directory that contains the schema files defining tables, views, and stored procedures. |
BrowsableSchemas | This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC. |
Tables | This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC. |
Views | Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC. |
A path to the directory that contains the schema files defining tables, views, and stored procedures.
string
"%APPDATA%\\CData\\Asana Data Provider\\Schema"
The path to a directory which contains the schema files for the Cloud (.rsd files for tables and views, .rsb files for stored procedures). The folder location can be a relative path from the location of the executable. The Location property is only needed if you want to customize definitions (for example, change a column name, ignore a column, and so on) or extend the data model with new tables, views, or stored procedures.
If left unspecified, the default location is "%APPDATA%\\CData\\Asana Data Provider\\Schema" with %APPDATA% being set to the user's configuration directory:
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 property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC.
string
""
Listing the tables from some databases can be expensive. Providing a list of tables in the connection string improves the performance of the Cloud.
This property can also be used as an alternative to automatically listing views if you already know which ones you want to work with and there would otherwise be too many to work with.
Specify the tables you want in a comma-separated list. Each table should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Tables=TableA,[TableB/WithSlash],WithCatalog.WithSchema.`TableC With Space`.
Note that when connecting to a data source with multiple schemas or catalogs, you will need to provide the fully qualified name of the table in this property, as in the last example here, to avoid ambiguity between tables that exist in multiple catalogs or schemas.
Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC.
string
""
Listing the views from some databases can be expensive. Providing a list of views in the connection string improves the performance of the Cloud.
This property can also be used as an alternative to automatically listing views if you already know which ones you want to work with and there would otherwise be too many to work with.
Specify the views you want in a comma-separated list. Each view should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Views=ViewA,[ViewB/WithSlash],WithCatalog.WithSchema.`ViewC With Space`.
Note that when connecting to a data source with multiple schemas or catalogs, you will need to provide the fully qualified name of the table in this property, as in the last example here, to avoid ambiguity between tables that exist in multiple catalogs or schemas.
This section provides a complete list of the Caching properties you can configure in the connection string for this provider.
Property | Description |
AutoCache | Automatically caches the results of SELECT queries into a cache database specified by either CacheLocation or both of CacheConnection and CacheProvider . |
CacheLocation | Specifies the path to the cache when caching to a file. |
CacheTolerance | The tolerance for stale data in the cache specified in seconds when using AutoCache . |
Offline | Use offline mode to get the data from the cache instead of the live source. |
CacheMetadata | This property determines whether or not to cache the table metadata to a file store. |
Automatically caches the results of SELECT queries into a cache database specified by either CacheLocation or both of CacheConnection and CacheProvider .
bool
false
When AutoCache = true, the Cloud automatically maintains a cache of your table's data in the database of your choice.
When AutoCache = true, the Cloud caches to a simple, file-based cache. You can configure its location or cache to a different database with the following properties:
Specifies the path to the cache when caching to a file.
string
"%APPDATA%\\CData\\Asana Data Provider"
The CacheLocation is a simple, file-based cache.
If left unspecified, the default location is "%APPDATA%\\CData\\Asana Data Provider" with %APPDATA% being set to the user's configuration directory:
The tolerance for stale data in the cache specified in seconds when using AutoCache .
int
600
The tolerance for stale data in the cache specified in seconds. This only applies when AutoCache is used. The Cloud checks with the data source for newer records after the tolerance interval has expired. Otherwise, it returns the data directly from the cache.
Use offline mode to get the data from the cache instead of the live source.
bool
false
When Offline = true, all queries execute against the cache as opposed to the live data source. In this mode, certain queries like INSERT, UPDATE, DELETE, and CACHE are not allowed.
This property determines whether or not to cache the table metadata to a file store.
bool
false
As you execute queries with this property set, table metadata in the Asana catalog are cached to the file store specified by CacheLocation if set or the user's home directory otherwise. A table's metadata will be retrieved only once, when the table is queried for the first time.
The Cloud automatically persists metadata in memory for up to two hours when you first discover the metadata for a table or view and therefore, CacheMetadata is generally not required. CacheMetadata becomes useful when metadata operations are expensive such as when you are working with large amounts of metadata or when you have many short-lived connections.
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 rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time. |
Other | These hidden properties are used only in specific use cases. |
PseudoColumns | This property indicates whether or not to include pseudo columns as columns to the table. |
Readonly | You can use this property to enforce read-only access to Asana from the provider. |
RTK | The runtime key used for licensing. |
Timeout | The value in seconds until the timeout error is thrown, canceling the operation. |
UserDefinedViews | A filepath pointing to the JSON configuration file containing your custom views. |
Limits the number of rows returned rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time.
int
-1
Limits the number of rows returned rows when no aggregation or group by is used in the query. This helps avoid performance issues at design time.
These hidden properties are used only in specific use cases.
string
""
The properties listed below are available for specific use cases. Normal driver use cases and functionality should not require these properties.
Specify multiple properties in a semicolon-separated list.
DefaultColumnSize | Sets the default length of string fields when the data source does not provide column length in the metadata. The default value is 2000. |
ConvertDateTimeToGMT | Determines whether to convert date-time values to GMT, instead of the local time of the machine. |
RecordToFile=filename | Records the underlying socket data transfer to the specified file. |
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, "*=*".
You can use this property to enforce read-only access to Asana from the provider.
bool
false
If this property is set to true, the Cloud will allow only SELECT queries. INSERT, UPDATE, DELETE, and stored procedure queries will cause an error to be thrown.
The runtime key used for licensing.
string
""
The RTK property may be used to license a build.
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.
A filepath pointing to the JSON configuration file containing your custom views.
string
""
User Defined Views are defined in a JSON-formatted configuration file called UserDefinedViews.json. The Cloud automatically detects the views specified in this file.
You can also have multiple view definitions and control them using the UserDefinedViews connection property. When you use this property, only the specified views are seen by the Cloud.
This User Defined View configuration file is formatted as follows:
For example:
{ "MyView": { "query": "SELECT * FROM projects WHERE MyColumn = 'value'" }, "MyView2": { "query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)" } }Use the UserDefinedViews connection property to specify the location of your JSON configuration file. For example:
"UserDefinedViews", "C:\\Users\\yourusername\\Desktop\\tmp\\UserDefinedViews.json"