Create a connection to Freshdesk by navigating to the Connections page in the Sync App application and selecting the corresponding icon in the Add Connections panel. If the Freshdesk icon is not available, click the Add More icon to download and install the Freshdesk connector from the CData site.

Required properties are listed under the Settings tab. The Advanced tab lists connection properties that are not typically required.

Connecting to Freshdesk

Freshdesk makes use of basic authentication. To connect to data, set the following connection properties:

• Domain: Set this to the domain associated with your Freshdesk account. For example, in your URL, https://{domainValue}.freshdesk.com, thus the connection string should be:

  Domain=domainValue

• APIKey: Set this to the API key associated with your Freshdesk account. To retrieve your API key, log in to your support Portal. Click the profile picture in the upper-right corner and select the profile settings page. The API key is available below the change password section to the right.

This section details a selection of advanced features of the Freshdesk Sync App.

User Defined Views

The Sync App 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.

SSL Configuration

Use SSL Configuration to adjust how Sync App handles TLS/SSL certificate negotiations. You can choose from various certificate formats; see the SSLServerCert property under "Connection String Options" for more information.

Firewall and Proxy

Configure the Sync App for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.

Query Processing

The Sync App offloads as much of the SELECT statement processing as possible to Freshdesk and then processes the rest of the query in memory (client-side).

See Query Processing for more information.

Logging

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.

Customizing the SSL Configuration

By default, the Sync App 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.

Connecting Through a Firewall or Proxy

HTTP Proxies

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.

Other Proxies

Set the following properties:

• To use a proxy-based firewall, set FirewallType, FirewallServer, and FirewallPort.
• To tunnel the connection, set FirewallType to TUNNEL.
• To authenticate, specify FirewallUser and FirewallPassword.
• To authenticate to a SOCKS proxy, additionally set FirewallType to SOCKS5.

Overview

This section shows the available API objects and provides more information on executing SQL to Freshdesk APIs.

Key Features

• The Sync App models Freshdesk entities as relational tables, allowing you to write SQL to query Freshdesk data.
• Live connectivity to these objects means any changes to your Freshdesk account are immediately reflected when using the Sync App.

Tables

Tables describes the available tables. Tables are statically defined to model Tickets, Conversations, Agents, and more.

The Sync App models the data in Freshdesk into a list of tables that can be queried using standard SQL statements.

Generally, querying Freshdesk 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.

Freshdesk Connector for CData Sync Tables

Update, delete, and query from agents table

Table Specific Information

Select

The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App. For example, the following query is processed server side:

SELECT * FROM Agents WHERE Id = 100

Note: To query Agents table, All Agent APIs other than the Currently Authenticated Agent API require admin privileges.

Update

Following is an example of how to update an agent:

UPDATE Agents SET GroupIdsAggregate = '111' WHERE Id = 100

Delete

Following is an example of how to delete an agent:

DELETE FROM Agents WHERE Id = 100

Columns

Query from BusinessHours table

Table Specific Information

Note: Only users with admin privileges can access the following Table.

Select

Following is an example to select all entries from BusinessHours table:

SELECT * FROM BusinessHours

You can also select a specific entry from BusinessHours table:

SELECT * FROM BusinessHours WHERE Id = 100

Columns

Create, update and query from CannedResponses table

Table Specific Information

Note: Only users with admin privileges can access the following Table.

Select

To query the CannedResponses table, FolderId should be mentioned in the WHERE clause. For example:

SELECT * FROM CannedResponses WHERE FolderId = 100

Insert

FolderId, Visibility, Title and ContentHTML are mandatory columns for Inserting into CannedResponses tables. For example:

INSERT INTO CannedResponses (Title, ContentHTML, Visibility, FolderId) VALUES (Sample response, 'this is also a new sample response', 0, 100)

Update

Following is an example to update a row in CannedResponses table:

UPDATE CannedResponses SET Title = 'Updated title' WHERE Id = 100

Columns

Query from CannedResponsesFolder table

Table Specific Information

Note: Only users with admin privileges can access the following Table.

Select

Following is an example to select all entries from CannedResponsesFolder table:

SELECT * FROM CannedResponsesFolder

You can also select a specific entry from CannedResponsesFolder table:

SELECT * FROM CannedResponsesFolder WHERE Id = 100

Insert

Name is a mandatory columns for Inserting into CannedResponsesFolder table.

INSERT INTO CannedResponsesFolder (Name) VALUES (directoryA)

Update

Following is an example to update CannedResponsesFolder:

UPDATE CannedResponsesFolder SET Name = 'updated name' WHERE Id = 100

Columns

Create, update, delete, and query from companies table

Table Specific Information

Select

The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App. For example, the following query is processed server side:

SELECT * FROM Companies WHERE CreatedAt >= '2017-10-01' AND CreatedAt <= '2017-10-07'

The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The following columns can be used:

• Id
• DomainAggregate
• CreatedAt
• UpdatedAt

Note: To filter all companies created on a specific day (e.g: 2019-09-23), query should be structured as:

WHERE CreatedAt >= '2019-09-22' AND CreatedAt <= '2019-09-24' 

Insert

Name is mandatory for creating a new company. Following is an example of creating a new company:

INSERT INTO Companies (Name, Description) Values ('Example', 'Example description of new company')

Update

Following is an example of how to update a company:

UPDATE Companies SET Description = 'New description' WHERE Id = 786

Delete

Following is an example of how to delete from Companies table:

DELETE FROM Companies WHERE Id = 786

Columns

Create, update, delete, and query from contacts table

Table Specific Information

Select

The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App. For example, the following query is processed server side:

SELECT * FROM Contacts WHERE Active = false AND (Email = '[email protected]' OR CompanyId = 1)

The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The following columns can be used:

• Id
• Active
• CompanyId
• Email
• Language
• Tag
• TimeZone
• CreatedAt
• UpdatedAt

Note: To filter all contacts created on a specific day (e.g: 2019-09-23), query should be structured as:

WHERE CreatedAt >= '2019-09-22' AND CreatedAt <= '2019-09-24'

Insert

Name and Email are mandatory for creating a new contact. Following is an example of creating a new contact:

INSERT INTO Contacts (Name, Email, Language) Values ('Example', '[email protected]', 'English')

Update

Following is an example of how to update a contact:

UPDATE Contacts SET Active = true WHERE Id = 786

Delete

Following is an example of how to delete from Contacts table:

DELETE FROM Contacts WHERE Id = 786

Columns

Delete, and query from conversations table

Table Specific Information

Select

To query the Conversations table, TicketId should be mentioned in the WHERE clause. For example:

SELECT * FROM Conversations WHERE TicketId = 100

Note: The Conversations table can only be filtered on TicketId.

Delete

Following is an example of how to delete from the Conversations table:

DELETE FROM Conversations WHERE Id = 786

Columns

Create, update, delete, and query from groups table

Table Specific Information

Select

The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App. For example, the following query is processed server side:

SELECT * FROM Groups WHERE Id = 100

Note: Only users with admin privileges can access this Table.

Insert

Name is a mandatory column for inserting into Groups table. For example:

INSERT INTO Groups (Name, Description, AutoTicketAssign) VALUES ('Example', 'Example Description...', false)

Update

Following is an example of how to update a group:

UPDATE Groups SET Description = 'New description...' WHERE Id = 100

Delete

Following is an example of how to delete from Groups table:

DELETE FROM Groups WHERE Id = 786

Columns

Create, update, delete, and query from Mailboxes table

Table Specific Information

Note: Only users with admin privileges can access the following Table.

Select

Following is an example to select all entries from Mailboxes table:

SELECT * FROM Mailboxes

The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The filters listed can also be combined using AND OR. The following columns can be used:

• Id
• SupportEmail
• ForwardEmail
• ProductId
• GroupId
• Active

Insert

SupportEmail and MailboxType are mandatory to Insert into Mailboxes table. For instance:

INSERT INTO Mailboxes (SupportEmail, Name, MailboxType) Values ('[email protected]', 'Test', 'freshdesk_mailbox')

Update

UPDATE Mailboxes SET Name = 'Test mailbox' WHERE Id = 786

Delete

Following is an example of how to delete from the Mailboxes table:

DELETE FROM Mailboxes WHERE Id = 786

Columns

Query from products table

Table Specific Information

Note: Only users with admin privileges can access the following Table.

Select

Following is an example to select all entries from Products table:

SELECT * FROM Products

You can also select a specific entry from Products table:

SELECT * FROM Products WHERE Id = 100

Columns

Query from roles table

Table Specific Information

Select

The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App. For example, the following query is processed server side:

SELECT * FROM Roles WHERE Id = 100

Note: Only users with admin privileges can access the following Table. Following is an example of selecting a role:

Columns

Create, update, delete, and query from skills table

Table Specific Information

Select

Following is an example to select all entries from Skills table:

SELECT * FROM Skills

You can also select a specific entry from Skills table:

SELECT * FROM Skills WHERE Id = 73000001322

Insert

Name is mandatory for creating a new skill. Following is an example of creating a new skill:

INSERT INTO Skills (Name) Values ('Example')

Update

Following is an example of how to update a skill:

UPDATE Skills SET Name = 'New name' WHERE Id = 73000001322

Delete

Following is an example of how to delete from Skills table:

DELETE FROM Skills WHERE Id = 73000001322

Columns

Query, Create and Update SLAPolicies table

Table Specific Information

Note: Only users with admin privileges can access the following Table.

Select

Following is an example to select all entries from SLAPolicies table:

SELECT * FROM SLAPolicies

You can also select a specific entry from SLAPolicies table:

SELECT * FROM SLAPolicies WHERE Id = 100

Columns

Query from surveys table

Table Specific Information

Select

Following is an example to select all entries from Surveys table:

SELECT * FROM Surveys

You can also select a specific entry from Surveys table:

SELECT * FROM Surveys WHERE Id = 73000092562

Columns

Query from ticketFields table

Table Specific Information

Note: Users whose credentials (identified by the API key) are used to access the Table should be authorised to either view the ticket fields or create a new ticket.

Select

The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support client side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed server side within the Sync App. For example, the following query is processed server side:

SELECT * FROM TicketFields WHERE Type = 'default_requester'

The Freshdesk API allows only the following column(s) to be used as filter criteria in the WHERE clause:

• Type

Insert

Label, LabelForCustomers and Type are mandatory columns for Inserting into TicketFields table.

INSERT INTO TicketFields (Label, LabelForCustomers, Type) VALUES ('labelA', 'labelA', custom_text)

Update

Following is an example to update TicketFields:

UPDATE TicketFields SET Label = 'updated label' WHERE Id = 100

Delete

Following is an example to delete a TicketFields:

DELETE FROM TicketFields WHERE Id = 100

Columns

Create, update, delete, and query from tickets table

Table Specific Information

Select

The Sync App will use the Freshdesk API to process WHERE clause conditions built with the following columns and operators. Most of the columns support server side filtering with the following operators: =,>,<,<=,>=,AND,OR. The rest of the filter is executed client side within the Sync App. For example, the following query is processed server side:

SELECT * FROM Tickets WHERE Status = 2 AND (Priority = 1 OR Type = 'Other')

The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The following columns can be used:

• Id
• AgentId
• GroupId
• Priority
• Status
• Tag
• Type
• DueBy
• FirstResponseDueBy
• CreatedAt
• UpdatedAt

Insert

Email, Subject, Description, GroupId, Status and Priority are mandatory columns for Inserting/Creating a new ticket.

Every ticket uses fixed numerical values to denote its Status and Priority. Numerical values are given as:

Status:

• Open = 2
• Pending = 3
• Resolved = 4
• Closed = 5

Priority:

• Low = 1
• Medium = 2
• High = 3
• Urgent = 4

A new ticket can be inserted as following:

INSERT INTO Tickets (Description, Subject, Email,  GroupId, Status, Priority) VALUES ('Details about the issue...', 'New support needed...', '[email protected]', 12345, 3, 2)

Update

Following is an example to update a ticket:

UPDATE Tickets SET Priority = 1 WHERE Id = 100

Delete

Following is an example to delete a ticket:

DELETE FROM Tickets WHERE Id = 100

Columns

Create, update, delete, and query from TimeEntries table

Table Specific Information

Select

Following is an example to select all entries from TimeEntries table:

SELECT * FROM TimeEntries

The API allows only a subset of columns to be used as filter criteria in the WHERE clause. The following columns can be used:

• AgentId
• Billable
• ExecutedAt

Insert

TicketId is mandatory to Insert into TimeEntries table. For instance:

INSERT INTO TimeEntries (TicketId, Note, AgentId) Values ('255', 'Invoice Information', '122')

Note:

• The TicketId is required field to Insert into TimeEntries table.
• Default value for Billable is true.
• If the TimeSpent attribute and the TimerRunning attribute are not specified, then the TimerRunning attribute will automatically be set to 'true'.
• If the StartTime is specified and the TimerRunning attribute is not specified, then the TimerRunning attribute will automatically be set to 'true'.
• The StartTime cannot be greater than the current time.
• The StartTime cannot be given in the query if the TimerRunning attribute is set to 'false'

Update

UPDATE TimeEntries SET Billable = 'true' WHERE Id = 786

Note:

• The StartTime cannot be updated if the timer is already running.
• The StartTime cannot be be updated unless the timer_running attribute is updated from 'true' to 'false'.
• The StartTime cannot be greater than the current time.
• The TimerRunning attribute cannot be set to the same value as before.
• The AgentId cannot be updated if the timer is already running.

Delete

Following is an example of how to delete from the TimeEntries table:

DELETE FROM TimeEntries WHERE Id = 786

Columns

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.

Freshdesk Connector for CData Sync Views

Retrieve the available Custom Objects in FreshDesk.

Table Specific Information

Select

Following is an example to select all entries from the CustomObjects table:

SELECT * FROM CustomObjects

You can also select a specific entry from the CustomObjects table:

SELECT * FROM CustomObjects WHERE Id = 11704

Columns

Query the TicketActivities view.

Table Specific Information

Select

Following is an example to select all entries from the TicketActivities table:

SELECT * FROM TicketActivities

Columns

Query the TicketProperties view.

Columns

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.

Authentication

SSL

Firewall

Proxy

Logging

Schema

Miscellaneous

This section provides a complete list of the Authentication properties you can configure in the connection string for this provider.

Domain is used for accessing your Freshdesk account.

Remarks

Domain is used for accessing your Freshdesk account. For example, in your URL: https://{domainValue}.freshdesk.com, thus connection string should be:

Domain=domainValue

The API key used for accessing your Freshdesk account.

Remarks

The API key used for accessing your Freshdesk account. The API key can be found in Freshdesk by going to Profile Settings -> API Key.

This section provides a complete list of the SSL properties you can configure in the connection string for this provider.

The certificate to be accepted from the server when connecting using TLS/SSL.

Remarks

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:

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.

The protocol used by a proxy-based firewall.

Remarks

This property specifies the protocol that the Sync App will use to tunnel traffic through the FirewallServer proxy. Note that by default, the Sync App connects to the system proxy; to disable this behavior and connect to one of the following proxy types, set ProxyAutoDetect to false.

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.

Remarks

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 Sync App uses the system proxy by default. To use a different proxy, set ProxyAutoDetect to false.

The TCP port for a proxy-based firewall.

Remarks

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.

Remarks

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.

Remarks

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.

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.

Remarks

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.

Remarks

The hostname or IP address of a proxy to route HTTP traffic through. The Sync App 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 Sync App uses the system proxy. If you need to use another proxy, set ProxyAutoDetect to false.

The TCP port the ProxyServer proxy is running on.

Remarks

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.

Remarks

This value specifies the authentication type to use to authenticate to the HTTP proxy specified by ProxyServer and ProxyPort.

Note that the Sync App 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:

• BASIC: The Sync App performs HTTP BASIC authentication.
• DIGEST: The Sync App performs HTTP DIGEST authentication.
• NEGOTIATE: The Sync App retrieves an NTLM or Kerberos token based on the applicable protocol for authentication.
• PROPRIETARY: The Sync App does not generate an NTLM or Kerberos token. You must supply this token in the Authorization header of the HTTP request.

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.

Remarks

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.

Remarks

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 Sync App 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.

Remarks

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:

A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the ProxyServer .

Remarks

The ProxyServer is used for all addresses, except for addresses defined in this property. Use semicolons to separate entries.

Note that the Sync App 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.

Core modules to be included in the log file.

Remarks

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.

This section provides a complete list of the Schema properties you can configure in the connection string for this provider.

A path to the directory that contains the schema files defining tables, views, and stored procedures.

Remarks

The path to a directory which contains the schema files for the Sync App (.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\\FreshDesk 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.

Remarks

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.

Remarks

Listing the tables from some databases can be expensive. Providing a list of tables in the connection string improves the performance of the Sync App.

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.

Remarks

Listing the views from some databases can be expensive. Providing a list of views in the connection string improves the performance of the Sync App.

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 Miscellaneous properties you can configure in the connection string for this provider.

Use FetchTicketsUpdatedSince to query tickets older than 30 days. Note: TicketStats must be set to True.

Remarks

When TicketStats = true, all requests (including filtering request) would be sent to the 'List all' endpoint. The 'List all' endpoint only retrieves the tickets created in the last 30 days, unless FetchTicketsUpdatedSince is set to a specifed date. Set FetchTicketsUpdatedSince to a specified date to retrieve tickets created past the last 30 days. (Example: FetchTicketsUpdatedSince=2022-01-01 or FetchTicketsUpdatedSince=2022-01-01T00:00:00Z)

Use IgnoreSurplusResults to ignore results beyond 300 which have same CreatedAt value.

Remarks

By default, FreshDesk API only returns upto 300 results matching a specific filter. Paging mechanism of the driver uses CreatedAt attribute as a filter, thus more than 300 results with same CreateAt value will cause paging to fail. IgnoreSurplusResults will cause these surplus results to be ignored without causing an exception and keep retrieving results.

Whether to include custom objects or not.

Remarks

If set to TRUE, the custom objects are retrieved. Note: You must have the Custom Objects feature enabled to use this property.

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.

Remarks

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.

Remarks

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.

Integration and Formatting

This property indicates whether or not to include pseudo columns as columns to the table.

Remarks

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, "*=*".

Set this property to control the number of rows scanned when TypeDetectionScheme is set to RowScan.

Remarks

Determines the number of rows used to determine the column data types.

Setting a high value may decrease performance. Setting a low value may prevent the data type from being determined properly, especially when there is null data.

Use TicketPropertiesURL to query ticket properties.

Remarks

Set TicketPropertiesURL to the API URL that is found on the Schedule page of the created Scheduled Export. To find this, go to Reports/Schedule an export/Click on the name of the Schedule and the URL is under the Receive via API section.

Use TicketsStats to retrieve stats attributes of a ticket, which are not normally available.

Remarks

When TicketStats = true, all requests (including filtering request) would be sent to the 'List all' endpoint. This would slightly affect the performance by handling filtering client-side, but would retrieve stats attributes of each ticket. 'List all' endpoint only retrieves the tickets created in the last 30 days.

The value in seconds until the timeout error is thrown, canceling the operation.

Remarks

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 Sync App throws an exception.

Determines how to determine the data type of columns.

Remarks

A filepath pointing to the JSON configuration file containing your custom views.

Remarks

User Defined Views are defined in a JSON-formatted configuration file called UserDefinedViews.json. The Sync App 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 Sync App.

This User Defined View configuration file is formatted as follows:

• Each root element defines the name of a view.
• Each root element contains a child element, called query, which contains the custom SQL query for the view.

For example:

{
	"MyView": {
		"query": "SELECT * FROM Tickets WHERE MyColumn = 'value'"
	},
	"MyView2": {
		"query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
	}
}

"UserDefinedViews", "C:\\Users\\yourusername\\Desktop\\tmp\\UserDefinedViews.json"