Invantive Bridge
Connector Teamleader: Teamleader is a cloud solution for customer management. Teamleader includes CRM as well as project and tickets. Teamleader can be extended by defining custom fields on several core concepts. |
Teamleader is a cloud solution for customer management. Teamleader includes CRM as well as project and tickets. Teamleader can be extended by defining custom fields on several core concepts.
Code for use in settings.xml: Teamleader
Alias: teamleader
Abbreviation: tlr
Status: Production
Available in Editions: Paid
String-comparison is Case-sensitive: true
Use Catalog in Full Name: true
Use Schema in Full Name: true
Technical Documentation: https://apidocs.teamleader.be/
Documentation
Authentication
Authentication can be done using one of the following two alternatives:
1. Using the user log on code and password also used on the Teamleader website.
2. Using an API group and API secret.
Authentication using user log on code and password is recommended for general use. The user must have access to all functionality since by default all so-called 'scopes' are requested. The scopes can be manually entered to be able to log in with a restricted accounts. Please provide a space-separated list chosen from companies, contacts, deals, departments, events, invoices, products, projects, quotations, subscriptions, tickets, todos, users.
The API group and secret can be found on https://app.teamleader.eu/apiwebhooks.php?show_key.
Usage Limits
Invantive UniversalSQL executes API calls to retrieve and upload data. The number of API calls allowed per 5 seconds is 25. Invantive UniversalSQL ensures that within your session the number of calls allowed per hour is not exceeded.
To get an impression of how Invantive UniversalSQL translates into API calls, please query the data dictionary view 'sessionios', such as with 'select * from sessionios@datadictionary'.
Custom Fields
Custom fields for which one value can be entered on an object are added to the table representing the object. For instance, a custom field 'needsaudit' on 'project', will be added as a column 'c_needsaudit' on the 'project' table. The name of the additional column directly derives from the custom field name. Almost all changes, including adding numbers or reading characters, will result in the data model being changed.
Custom fields which can have no, one or multiple values ('set' custom fields) are reflected in the data model by tables with a name constructed of the object name, an underscore plus the name of the custom field. For example, a custom field named 'Multiple Selection' on 'Task' will add a table 'task_multipleselection' to the data model.
Custom fields are unique to each Teamleader environment. When the existence of specific custom field is not guaranteed, please use generic solutions like the tables 'CustomFieldDefinitions', 'custom_fields', 'custom_field_options', 'custom_field', 'Custom_Fields_All', 'Custom_Field_Types' and their object-specific custom field value tables like 'ticket_custom_field_values_by_id'.
Connector Attributes
The Teamleader connector can be configured using the following attributes:
Code |
Description |
Default Value |
Set from Connection String |
Set from Set SQL-Statement |
Set from Connectors File |
Set from Log On |
|---|---|---|---|---|---|---|
force-custom-field-to-string |
Whether to force custom field values shown in columns to be represented as string instead of the registered type. |
False |
✓ |
|
✓ |
✓ |
scopes |
Space-separated and case-sensitive list of scope for OAuth only. Leave empty for all. |
|
✓ |
|
✓ |
✓ |
api-client-id |
The client ID is a unique identifier of your application. It is generated by registering an application. |
|
✓ |
|
✓ |
✓ |
api-client-secret |
The client secret is to be kept confidential. Such as a password for a logon code, the client secret is the confidential part of an app identified by a client ID. It is needed during the OAuth2 Code Grant Flow together with the refresh token to get access. |
*** |
✓ |
|
✓ |
✓ |
api-refresh-token |
Refresh Token is a security token for the OAuth2 Code Grant Flow. With a Refresh Token and client secret you can retrieve a renewed access token to access protected resources. A Refresh Token and client secret must be stored securely since once compromised allows access to your protected resources. |
*** |
✓ |
|
✓ |
✓ |
api-redirect-url |
The redirect URI is the website a browser session is redirected to after the OAuth2 authentication process has been completed. |
|
✓ |
|
✓ |
✓ |
api-group-authentication |
Use API group authentication when true. OAuth otherwise. |
|
✓ |
|
✓ |
|
api-scope |
The scope to request an OAuth token for. |
|
✓ |
|
✓ |
|
api-token-url |
The token URI is the OAuth2 endpoint to exchange tokens. |
|
✓ |
|
✓ |
|
api-url |
URL to access the API. |
|
✓ |
|
✓ |
|
bulk-delete-page-size-rows |
Number of rows to delete per batch when bulk deleting |
10000 |
✓ |
✓ |
✓ |
|
bulk-insert-page-size-bytes |
Approximate maximum size in bytes of batch when bulk inserting |
10000000 |
✓ |
✓ |
✓ |
|
bulk-insert-page-size-rows |
Number of rows to insert per batch when bulk inserting |
250 |
✓ |
✓ |
✓ |
|
download-error-400-bad-request-max-tries |
Maximum number of tries when OData server reports bad format during retrieval of data. |
30 |
✓ |
✓ |
✓ |
|
download-error-400-bad-request-sleep-initial-ms |
Initial sleep in milliseconds between retries when OData server reports that the API server is unavailable during retrieval of data. |
5000 |
✓ |
✓ |
✓ |
|
download-error-400-bad-request-sleep-max-ms |
Maximum sleep in milliseconds between retries when OData server reports that the API server is unavailable during retrieval of data. |
60000 |
✓ |
✓ |
✓ |
|
download-error-400-bad-request-sleep-multiplicator |
Multiplication factor for sleep between retries OData server reports that the API server is unavailable during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-422-bad-request-max-tries |
Maximum number of tries when OData server reports unprocessable entity during retrieval of data. |
30 |
✓ |
✓ |
✓ |
|
download-error-422-bad-request-sleep-initial-ms |
Initial sleep in milliseconds between retries when OData server reports unprocessable entity during retrieval of data. |
5000 |
✓ |
✓ |
✓ |
|
download-error-422-bad-request-sleep-max-ms |
Maximum sleep in milliseconds between retries when OData server reports unprocessable entity during retrieval of data. |
60000 |
✓ |
✓ |
✓ |
|
download-error-422-bad-request-sleep-multiplicator |
Multiplication factor for sleep between retries OData server reports unprocessable entity during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-429-too-many-requests-max-tries |
Maximum number of tries when the website reports that too many requests have been made during a timeslot of one minute or one day. |
10 |
✓ |
✓ |
✓ |
|
download-error-429-too-many-requests-sleep-initial-ms |
Initial sleep in milliseconds between retries when the website reports that too many requests have been made during a timeslot of one minute or one day. |
5000 |
✓ |
✓ |
✓ |
|
download-error-429-too-many-requests-sleep-max-ms |
Maximum sleep in milliseconds between retries when the website reports that too many requests have been made during a timeslot of one minute or one day. |
60000 |
✓ |
✓ |
✓ |
|
download-error-429-too-many-requests-sleep-multiplicator |
Multiplication factor for sleep between retries when the website reports that too many requests have been made during a timeslot of one minute or one day. |
2 |
✓ |
✓ |
✓ |
|
download-error-502-server-unavailable-max-tries |
Maximum number of tries when OData server reports a bad gateway during retrieval of data. |
30 |
✓ |
✓ |
✓ |
|
download-error-502-server-unavailable-sleep-initial-ms |
Initial sleep in milliseconds between retries when OData server reports a bad gateway during retrieval of data. |
10000 |
✓ |
✓ |
✓ |
|
download-error-502-server-unavailable-sleep-max-ms |
Maximum sleep in milliseconds between retries when OData server reports that a bad gateway during retrieval of data. |
60000 |
✓ |
✓ |
✓ |
|
download-error-502-server-unavailable-sleep-multiplicator |
Multiplication factor for sleep between retries OData server reports a bad gateway during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-503-server-unavailable-max-tries |
Maximum number of tries when OData server reports that the API server is unavailable during retrieval of data. |
30 |
✓ |
✓ |
✓ |
|
download-error-503-server-unavailable-sleep-initial-ms |
Initial sleep in milliseconds between retries when OData server reports that the API server is unavailable during retrieval of data. |
5000 |
✓ |
✓ |
✓ |
|
download-error-503-server-unavailable-sleep-max-ms |
Maximum sleep in milliseconds between retries when OData server reports that the API server is unavailable during retrieval of data. |
60000 |
✓ |
✓ |
✓ |
|
download-error-503-server-unavailable-sleep-multiplicator |
Multiplication factor for sleep between retries OData server reports that the API server is unavailable during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-504-gateway-timeout-max-tries |
Maximum number of tries when the website reports a gateway timeout. |
10 |
✓ |
✓ |
✓ |
|
download-error-504-gateway-timeout-sleep-initial-ms |
Initial sleep in milliseconds between retries when the website reports a gateway timeout. |
5000 |
✓ |
✓ |
✓ |
|
download-error-504-gateway-timeout-sleep-max-ms |
Maximum sleep in milliseconds between retries when the website reports a gateway timeout. |
60000 |
✓ |
✓ |
✓ |
|
download-error-504-gateway-timeout-sleep-multiplicator |
Multiplication factor for sleep between retries when the website reports a gateway timeout. |
2 |
✓ |
✓ |
✓ |
|
download-error-argument-exception-max-tries |
Maximum number of tries when an argument exception is returned when downloading a blob. |
10 |
✓ |
✓ |
✓ |
|
download-error-argument-exception-sleep-initial-ms |
Initial sleep in milliseconds between retries when an argument exception is returned when downloading a blob. |
1000 |
✓ |
✓ |
✓ |
|
download-error-argument-exception-sleep-max-ms |
Maximum sleep in milliseconds between retries when an argument exception is returned when downloading a blob. |
60000 |
✓ |
✓ |
✓ |
|
download-error-argument-exception-sleep-multiplicator |
Multiplication factor for sleep between retries when an argument exception is returned when downloading a blob. |
2 |
✓ |
✓ |
✓ |
|
download-error-internet-down-max-tries |
Maximum number of tries when the Internet connection seems down during retrieval of data. |
10 |
✓ |
✓ |
✓ |
|
download-error-internet-down-sleep-initial-ms |
Initial sleep in milliseconds between retries when the Internet connection seems down during retrieval of data. |
10000 |
✓ |
✓ |
✓ |
|
download-error-internet-down-sleep-max-ms |
Maximum sleep in milliseconds between retries when the Internet connection seems down during retrieval of data. |
60000 |
✓ |
✓ |
✓ |
|
download-error-internet-down-sleep-multiplicator |
Multiplication factor for sleep between retries when the Internet connection seems down during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-io-exception-max-tries |
Maximum number of tries when a network I/O connection failure occurs during retrieval of data. |
10 |
✓ |
✓ |
✓ |
|
download-error-io-exception-sleep-initial-ms |
Initial sleep in milliseconds between retries when a network I/O connection failure occurs during retrieval of data. |
10000 |
✓ |
✓ |
✓ |
|
download-error-io-exception-sleep-max-ms |
Maximum sleep in milliseconds between retries when a network I/O connection failure occurs during retrieval of data. |
60000 |
✓ |
✓ |
✓ |
|
download-error-io-exception-sleep-multiplicator |
Multiplication factor for sleep between retries when a network I/O connection failure occurs during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-json-exception-max-tries |
Maximum number of tries when an invalid JSON body is returned. |
3 |
✓ |
✓ |
✓ |
|
download-error-json-exception-sleep-initial-ms |
Initial sleep in milliseconds between retries when an invalid JSON body is returned. |
1000 |
✓ |
✓ |
✓ |
|
download-error-json-exception-sleep-max-ms |
Maximum sleep in milliseconds between retries when an invalid JSON body is returned. |
10000 |
✓ |
✓ |
✓ |
|
download-error-json-exception-sleep-multiplicator |
Multiplication factor for sleep between retries when an invalid JSON body is returned. |
2 |
✓ |
✓ |
✓ |
|
download-error-other-exception-max-tries |
Maximum number of tries when an unqualified error occurs during retrieval of data. |
3 |
✓ |
✓ |
✓ |
|
download-error-other-exception-sleep-initial-ms |
Initial sleep in milliseconds between retries when an unqualified error ocurrs during retrieval of data. |
5000 |
✓ |
✓ |
✓ |
|
download-error-other-exception-sleep-max-ms |
Maximum sleep in milliseconds between retries when an unqualified error ocurrs during retrieval of data. |
30000 |
✓ |
✓ |
✓ |
|
download-error-other-exception-sleep-multiplicator |
Multiplication factor for sleep between retries when an unqualified error ocurrs during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-socket-exception-max-tries |
Maximum number of tries when the network connection is forcible dropped during retrieval of data. |
10 |
✓ |
✓ |
✓ |
|
download-error-socket-exception-sleep-initial-ms |
Initial sleep in milliseconds between retries when the network connection is forcible dropped during retrieval of data. |
10000 |
✓ |
✓ |
✓ |
|
download-error-socket-exception-sleep-max-ms |
Maximum sleep in milliseconds between retries when the network connection is forcible dropped during retrieval of data. |
60000 |
✓ |
✓ |
✓ |
|
download-error-socket-exception-sleep-multiplicator |
Multiplication factor for sleep between retries when the network connection is forcible dropped during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-web-exception-max-tries |
Maximum number of tries when a web connection failure occurs during retrieval of data. |
10 |
✓ |
✓ |
✓ |
|
download-error-web-exception-sleep-initial-ms |
Initial sleep in milliseconds between retries when a web connection failure occurs during retrieval of data. |
10000 |
✓ |
✓ |
✓ |
|
download-error-web-exception-sleep-max-ms |
Maximum sleep in milliseconds between retries when a web connection failure occurs during retrieval of data. |
60000 |
✓ |
✓ |
✓ |
|
download-error-web-exception-sleep-multiplicator |
Multiplication factor for sleep between retries when a web connection failure occurs during retrieval of data. |
2 |
✓ |
✓ |
✓ |
|
download-error-web-not-implemented-max-tries |
Maximum number of tries when the connection reports not implemented. |
1 |
✓ |
✓ |
✓ |
|
download-error-web-not-implemented-sleep-initial-ms |
Initial sleep in milliseconds between retries when the connection reports not implemented. |
5000 |
✓ |
✓ |
✓ |
|
download-error-web-not-implemented-sleep-max-ms |
Maximum sleep in milliseconds between retries when the connection reports not implemented. |
60000 |
✓ |
✓ |
✓ |
|
download-error-web-not-implemented-sleep-multiplicator |
Multiplication factor for sleep between retries when the connection reports not implemented. |
2 |
✓ |
✓ |
✓ |
|
download-error-web-timeout-max-tries |
Maximum number of tries when the connection reports a timeout. |
10 |
✓ |
✓ |
✓ |
|
download-error-web-timeout-sleep-initial-ms |
Initial sleep in milliseconds between retries when the connection reports a timeout. |
5000 |
✓ |
✓ |
✓ |
|
download-error-web-timeout-sleep-max-ms |
Maximum sleep in milliseconds between retries when the connection reports a timeout. |
60000 |
✓ |
✓ |
✓ |
|
download-error-web-timeout-sleep-multiplicator |
Multiplication factor for sleep between retries when the connection reports a timeout. |
2 |
✓ |
✓ |
✓ |
|
download-error-web-unauthorized-max-tries |
Maximum number of tries when the connection reports an unauthorized error. |
1 |
✓ |
✓ |
✓ |
|
download-error-web-unauthorized-sleep-initial-ms |
Initial sleep in milliseconds between retries when the connection reports an unauthorized error. |
5000 |
✓ |
✓ |
✓ |
|
download-error-web-unauthorized-sleep-max-ms |
Maximum sleep in milliseconds between retries when the connection reports an unauthorized error. |
60000 |
✓ |
✓ |
✓ |
|
download-error-web-unauthorized-sleep-multiplicator |
Multiplication factor for sleep between retries when the connection reports an unauthorized error. |
2 |
✓ |
✓ |
✓ |
|
force-case-sensitive-identifiers |
Consider identifiers as case-sensitive independent of the platform capabilities. |
False |
✓ |
✓ |
✓ |
|
forced-casing-identifiers |
Forced casing of identifiers. Choose from Unset, Lower, Upper and Mixed. |
|
✓ |
✓ |
✓ |
|
http-disk-cache-compression-level |
Compression level for the HTTP disk cache, ranging from 1 (little) to 9 (intense). Default is 5. |
5 |
✓ |
✓ |
✓ |
|
http-disk-cache-directory |
Directory where HTTP cache is stored. |
C:\Users\gle3.WS212\Invantive\Cache\http\gle3\shared |
✓ |
✓ |
✓ |
|
http-disk-cache-ignore-write-errors |
Whether to ignore write errors to disk cache. |
False |
✓ |
✓ |
✓ |
|
http-disk-cache-max-age-sec |
Maximum acceptable age in seconds for use of data in the HTTP disk cache. |
2592000 |
✓ |
✓ |
✓ |
|
http-get-timeout-ms |
HTTP GET timeout (ms). |
300000 |
✓ |
✓ |
✓ |
|
http-memory-cache-compression-level |
Compression level for the HTTP memory cache, ranging from 1 (little) to 9 (intense). Default is 5. |
5 |
✓ |
✓ |
✓ |
|
http-memory-cache-max-age-sec |
Maximum acceptable age in seconds for use of data in the HTTP memory cache. |
14400 |
✓ |
✓ |
✓ |
|
http-post-timeout-ms |
HTTP POST timeout (ms). |
300000 |
✓ |
✓ |
✓ |
|
ignore-http-400-errors |
Ignore HTTP 400 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
ignore-http-401-errors |
Ignore HTTP 401 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
ignore-http-403-errors |
Ignore HTTP 403 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
ignore-http-404-errors |
Ignore HTTP 404 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
ignore-http-422-errors |
Ignore HTTP 422 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
ignore-http-429-errors |
Ignore HTTP 429 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
ignore-http-500-errors |
Ignore HTTP 500 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
ignore-http-502-errors |
Ignore HTTP 502 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
invalid-json-on-get-max-tries |
Maximum number of tries when the JSON received on GET is invalid. |
10 |
✓ |
✓ |
✓ |
|
invalid-json-on-get-sleep-initial-ms |
Initial sleep in milliseconds between retries when the JSON received on GET is invalid. |
10000 |
✓ |
✓ |
✓ |
|
invalid-json-on-get-sleep-max-ms |
Maximum sleep in milliseconds between retries when the JSON received on GET is invalid. |
60000 |
✓ |
✓ |
✓ |
|
invalid-json-on-get-sleep-multiplicator |
Multiplication factor for sleep between retries when the JSON received on GET is invalid. |
2 |
✓ |
✓ |
✓ |
|
invalid-json-on-post-max-tries |
Maximum number of tries when the JSON received on POST is invalid. |
1 |
✓ |
✓ |
✓ |
|
invalid-json-on-post-sleep-initial-ms |
Initial sleep in milliseconds between retries when the JSON received on POST is invalid. |
10000 |
✓ |
✓ |
✓ |
|
invalid-json-on-post-sleep-max-ms |
Maximum sleep in milliseconds between retries when the JSON received on POST is invalid. |
60000 |
✓ |
✓ |
✓ |
|
invalid-json-on-post-sleep-multiplicator |
Multiplication factor for sleep between retries when the JSON received on POST is invalid. |
2 |
✓ |
✓ |
✓ |
|
invantive-sql-correct-invalid-date |
Whether to correct invalid dates. |
False |
✓ |
✓ |
✓ |
|
invantive-sql-forward-filters-to-data-containers |
Whether to forward filters to data containers. |
True |
✓ |
✓ |
✓ |
|
invantive-sql-shuffle-fetch-results-data-containers |
Whether to shuffle results fetched from data containers. |
False |
✓ |
✓ |
✓ |
|
invantive-use-cache |
Whether to cache the results of a query. |
True |
✓ |
✓ |
✓ |
|
join-set-points-per-request |
Maximum number of values in a request when executing a join set. |
60 |
✓ |
✓ |
✓ |
|
limit-partition-calls-left |
Minimum number of remaining API calls on a partition towards a hard limit. When below, an error is raised. |
500 |
✓ |
✓ |
✓ |
|
log-native-calls-to-disk |
Registers native calls to data container backend as disk files. |
False |
✓ |
✓ |
✓ |
|
log-native-calls-to-trace |
Log native calls to data container backend on the trace. |
False |
✓ |
✓ |
✓ |
|
maximum-length-identifiers |
Non-default maximum length in characters of identifier names. |
|
✓ |
✓ |
✓ |
|
max-odata-filters |
The maximum number of OData filter elements. |
100 |
✓ |
✓ |
✓ |
|
max-url-length-accepted |
The maximum accepted URL length before raising an error. |
8000 |
✓ |
✓ |
✓ |
|
max-url-length-desired |
The maximum desired URL length. |
8000 |
✓ |
✓ |
✓ |
|
metadata-cache-max-age-sec |
Maximum acceptable age in seconds for re-use of metadata. |
|
✓ |
✓ |
✓ |
|
partition-slot-based-rate-limit-length-ms |
Total length in ms across all slots of a partition-based rate limit. |
60000 |
✓ |
|
✓ |
|
partition-slot-based-rate-limit-slots |
Number of slots per partition-based rate limit. Null means no slot-based rate limit |
|
✓ |
|
✓ |
|
pre-request-delay-ms |
Pre-request delay in milliseconds per request. |
0 |
✓ |
✓ |
✓ |
|
requested-page-size |
Preferred number of rows to exchange per round trip; only effective on limited platforms such as AFAS Online |
|
✓ |
✓ |
✓ |
|
requests-parallel-max |
Maximum number of parallel data requests from individual partitions on the data container. |
32 |
✓ |
✓ |
✓ |
|
simulate-http-400-errors |
Simulate HTTP 400 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
simulate-http-400-errors-percentage |
Percentage of simulated HTTP 400 errors when exchanging results with the OData endpoint. |
0 |
✓ |
✓ |
✓ |
|
simulate-http-401-errors |
Simulate HTTP 401 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
simulate-http-401-errors-percentage |
Percentage of simulated HTTP 401 errors when exchanging results with the OData endpoint. |
0 |
✓ |
✓ |
✓ |
|
simulate-http-403-errors |
Simulate HTTP 403 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
simulate-http-403-errors-percentage |
Percentage of simulated HTTP 403 errors when exchanging results with the OData endpoint. |
0 |
✓ |
✓ |
✓ |
|
simulate-http-429-errors |
Simulate HTTP 429 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
simulate-http-429-errors-percentage |
Percentage of simulated HTTP 429 errors when exchanging results with the OData endpoint. |
0 |
✓ |
✓ |
✓ |
|
simulate-http-500-errors |
Simulate HTTP 500 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
simulate-http-500-errors-percentage |
Percentage of simulated HTTP 500 errors when exchanging results with the OData endpoint. |
0 |
✓ |
✓ |
✓ |
|
simulate-http-502-errors |
Simulate HTTP 502 errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
simulate-http-502-errors-percentage |
Percentage of simulated HTTP 502 errors when exchanging results with the OData endpoint. |
0 |
✓ |
✓ |
✓ |
|
simulate-http-protocol-errors |
Simulate HTTP protocol errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
simulate-http-protocol-errors-percentage |
Percentage of simulated HTTP protocol errors when exchanging results with the OData endpoint. |
0 |
✓ |
✓ |
✓ |
|
simulate-http-timeout-errors |
Simulate HTTP timeout errors when exchanging results with the OData endpoint. |
False |
✓ |
✓ |
✓ |
|
simulate-http-timeout-errors-percentage |
Percentage of simulated HTTP timeout errors when exchanging results with the OData endpoint. |
0 |
✓ |
✓ |
✓ |
|
slot-based-rate-limit-length-ms |
Total length in ms across all slots of a slot-based rate limit. |
6000 |
✓ |
|
✓ |
|
slot-based-rate-limit-slots |
Number of slots of a slot-based rate limit. Null means no slot-based rate limit |
21 |
✓ |
|
✓ |
|
standardize-identifiers |
Rewrite all identifiers to the preferred standards as configured by standardize-identifiers-casing and maximum-length-identifiers. |
True |
✓ |
✓ |
✓ |
|
standardize-identifiers-casing |
Rewrite all identifiers to the recommended standard platform-specific casing when changing a data model on a case-dependent platform. |
True |
✓ |
✓ |
✓ |
|
use-batch-insert |
Whether to use batch insert. |
True |
✓ |
✓ |
✓ |
|
use-http-disk-cache-read |
Whether to use HTTP responses from previous queries stored on disk to answer the current query. |
True |
✓ |
✓ |
✓ |
|
use-http-disk-cache-write |
Whether to memorize HTTP responses on disk. |
True |
✓ |
✓ |
✓ |
|
use-http-memory-cache-read |
Whether to use HTTP responses from previous queries stored in memory that can answer the current query. |
True |
✓ |
✓ |
✓ |
|
use-http-memory-cache-write |
Whether to memorize HTTP responses from previous queries for use by future queries. |
True |
✓ |
✓ |
✓ |
|
10-09-2020 00:0920.1.206-BETA+2915
