The Telerik Platform product is retired.Learn more

Performance and Limitations

Performance and Limitations


When using Data Connectors, the performance depends highly on the transfer speed between Telerik Platform and your running instance of the Data Link Server. Another important factor is the transfer speed between the Data Link Server and your data store. Try to eliminate any bottlenecks that you may have between these pairs of services.


  • Granular permissions—currently granular permissions are not supported for content types linked to external data sources.
  • Owner role—the owner role and owner permissions are currently not supported for content types linked to external data sources.
  • Regular expressions support when filtering data from Data Connectors is limited to the following use cases. As a workaround, create a view or a stored procedure and map it to a Telerik Platform content type or cloud function respectively.
    • Starts with: ^searchstring (Example: var filter = {"name":{"$regex":"^John"}};)
    • Ends with: searchstring$ (Example: var filter = {"name":{"$regex":"John$"}};)
    • Contains: .*searchstring.* (Example: var filter = {"name":{"$regex":".*John.*"}};)
  • Passing regular expression options using the $options operator is not supported when filtering data from Data Connectors. Do not specify it, otherwise you will receive an incorrect result.
  • Cloud Code for Data events are only triggered when data is changed trough the Backend Services APIs. No events will be triggered if you change the data directly in the connected database or through another application that does not utilize the Backend Services APIs.

Data Store Limitations

  • Compound primary keys are not supported—currently only tables with single-column primary keys can be mapped to a content type. A possible workaround is to expose the data from such table via view with a single-column primary key (see below).
  • Database views are mapped to read-only content types
  • Database views—In order for read operations to work correctly, currently it is required that all views mapped to content types expose a single column, which identifies each row uniquely. To create a content type from a view, you have to manually map one of its columns to an Id field in the UI. In this case the content type is created as read-only and write operations are not possible.
  • Date formats without time zone—we assume that all of the legacy dates without time zone are stored in the UTC time standard.

See Also

Contact us: +1-888-365-2779
Copyright © 2016-2018, Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.