Key Capabilities and Data Sources supported in Dynamic Table
Updated
Overview
A Dynamic Table in Guided Workflow can be constructed using one of three data sources:
By Variable
By API
By Entity Type
Note: Each data source has specific features and limitations regarding Search, Filter, and Pagination.
Note: Across all three types of data sources, the default value selection is not supported in Dynamic Table, meaning we cannot pre-select a certain row.
Dynamic Table by Variable
The following are some of the functionalities of Dynamic Table by Variable
Search and Filter
These functionalities are not supported in Dynamic Tables constructed by Variable. The primary reason is technical limitations. To enable search and filtering, we would need to store the data using Elastic Search. Since Elastic Search is a database, storing this data in memory during runtime would significantly increase the server load, potentially slowing down the workflow or the system overall. Therefore, we do not support and will not support these features for Dynamic Tables by Variable.
Pagination
Pagination is supported. You can enable pagination and set the limit for the number of rows displayed per page. If pagination is disabled, all data will be displayed on a single sheet, which might not be practical for large datasets (Disabled Pagination means you’ll have only one sheet).
Output Format
When using a variable to construct a Dynamic Table, the output should always be an array of maps in a Value-Label format. This ensures that the data is structured correctly for display in the table.
Dynamic Table by API
The following section provides information on Dynamic Table by API.
Pre-requisite
To construct a Dynamic Table via API, it is mandatory to paginate the customer's API response. This means the API should return data in a paginated response structure.
Search and Filter
These features are supported in Dynamic Tables by API, but only if search and filter are supported at the API level. When making a search call, the API must have the capability to perform the search. Similarly, for filtering, the API should support filter operations. If the customer's API does not support search or filter, Sprinklr will not be able to provide these functionalities in the Dynamic Table.
Conditions:
The response structure from the API must be a paginated response.
Search and filter functionalities should be supported at the API level.
Pagination
Pagination in the Dynamic Table by API works similarly to the pagination described in the "By Variable" section. You can enable pagination and set the limit for the number of rows per page.
Dynamic Table by Entity Type
Note: This method involves fetching data from Sprinklr Entities (Entity Studio).
Search
Search functionality is supported if the 'Searchable' option is enabled for a particular column in Entity Studio. This option must be toggled ON for the column to be searchable in the Dynamic Table.
Filter and Pagination
Both filter and pagination functionalities are supported when constructing a Dynamic Table by Entity Type. You can enable these features as needed to manage and display the data effectively.