The Search Table action allows users to search for specific text within a table. By linking it to a Table component on the UI, the data in the table is filtered according to the search term entered in a Text Input field.

Technical Features

Real-time Filtering: The data in the table is filtered instantly.
Dynamic Search: Different results are displayed for each user entry.
UI-Based Selection: The table and input field to be searched are visually linked.‍
High Performance: Provides optimised search even in large data lists.

Search Table Action Application Steps

Log in to the Kuika platform.
Open the relevant project from the Apps screen.
Go to the UI Design module.
Open the Properties panel on the right side.
Add a Text Input component to be used for the search operation.

Add a Table component to list the data and link it to the relevant data source.
From the + ADD ACTION menu, add the Export > Search Table action according to the desired trigger event (Initial Actions, OnClick, OnBlur, etc.).

Parameter Definitions

Select a Table: Specifies the table to which the search operation will be applied.
Search Text: Specifies the input field where the user enters the search text.

Usage Scenario: Filtering List by Customer Name

The user wants to filter the customer list displayed on a screen by ‘Customer Name’. The customer list in the table should be dynamically updated according to each word entered in the search box.

Application Flow:

Elements:
- Text Input → ID: txtCustomerName
- Table → ID: table1
- Button → Label: ‘Search’
Action:
- The value entered in the txtCustomerName field is used to search the tableCustomerList table.
- An OnClick trigger is added to the Search button.
Add Action:
- OnClick → Export → Search Table
- Parameters:
  - Select a Table: table1
  - Search Text

Search Table Action Advanced Customisations

Real-Time Search: When used with the OnChange trigger, an automatic search can be performed with each keystroke.
Multi-Field Search: In future versions, simultaneous searches in multiple columns may be supported. In this case, a search parameter can be created from data from multiple Text Input fields (e.g., by combining them).
Comprehensive Filtering: The Search Table action can be used in a chain with more advanced filtering actions.

Technical Risks and Controls

Performance Issues: Instant search operations may slow down with very large data sets. Pagination and loading limits should be used.
Empty Input: When the search field is empty, old filters should be removed or all data should be reloaded.
Table ID Errors: Incorrect table selection or input ID definitions can cause errors. We recommend using the Symbol Picker.
Duplicate Results in the Same Data: Fields that are not filtered may appear in the search results. Review the columns on the UI.

The Search Table action enables users to perform fast and flexible searches in tables within the application. Optimised at both the interface and data layer, this action improves user experience, makes large data sets more accessible, and simplifies interactive listing operations.