Search Views
The search view displays data in a table with functions for adding, editing, deleting and filtering.
The search views can be used only for displaying data (read-only) or for displaying and modifying data. For more details about the visual representation of a search view the The Search View page in the User Interface chapter.
Functions of the search view
- Displaying the data as a table
- Filtering the data
- Selection: one by one, all visible rows, all rows that match a filter
- Add rows
- Edit, Delete and Custom actions on selected rows
- Paginating rows
- Execute global custom actions
- Auto-refresh when data changes (only monitors locally initialized changes)
How to use
To open the Search Views view, navigate to Develop ➔ Search Views.
Designer
Fields in the sidebar:
The title for the search view, as viewed by the user in the tab bar button.
Usually the title is the entity for which the search view is defined in plural form with the first letter in upper case. No restrictions are imposed on the title as it can contain spaces or any other special characters.
Eg.: the search view for the entity "product" should have the title "Products"
The list name is part of the URL for the search view.
The URL scheme for the search view is:
https://[instance-name]/[menu-name]/#search$[list-name]
Accessing the search view is done by entering the above URL in your browser. Another way to access the search view is by adding it to the menus.
The key name is the column name in the result set (of the FETCH query) that contains the key for each row. The search view uses the value of this column to create the identity of each row, which in turn is used to know the selected rows.
This field is optional but omitting it will disable the selection function on the search view.
The related edit view for the search view. It is used by the search view to handle the add, edit and delete functions.
This field is optional but omitting it will disable the add, edit and delete functions.
If the edit view is already defined it can be selected from the drop-down, if not it can be created by clicking the Navigate link.
The module to which the search view is part of. This field is optional.
It is used for the possibility of exporting the results in an Excel file.
The field is optional, but it must be filled with the value "1", for displaying the section Export with the button Excel.
The unique global identifier for the search view.
This field is automatically generated by the Link system module. This field is optional but omitting it will make the search view unsendable to another server.
Entity diagram:
FETCH tab
The fetch tab is used for writing the FETCH query that will extract the information that will be displayed in the search view.
After writing the FETCH query, click the Execute button, located above the query, to test the query. The result should appear under the query.
FILTERS tab
Fields in the filters table:
- Title - The title of the input field displayed to the user.
- Argument name - The name of the argument defined in the fetch.
- Input type - The input type displayed to the user.
- Catalog - The catalog. Used only for the FixedList and DynamicList input types.
- Operator - The filter operator.
- Property name - The property on which the operator is applied.
- Default value - The initial default value.
- Rank - The rank (order) to display the filters in order.
Tab entity diagram:
COLUMNS tab
Fields in the columns table:
- Display name - The title of the column displayed to the user.
- Column name - The name of the column as defined in fetch.
- View type - The view type.
- Navigate edit view - The edit view for navigating.
- Width (px) - The width, in pixels.
- Rank - The rank (order) of the column.
Tab entity diagram:
ACTIONS tab
Fields in the actions table:
- Action - The action. See actions for details.
Tab entity diagram:
CONFIG tab
The configuration tab is a JSON input in which you can enable or disable additional configuration options for the search view.
{
"sidebar.visible": true,
"sidebar.actions.visible": true, //Since 1.7.2
"table.buttons.add.visible": true, //Since 1.7.2
"table.buttons.delete.visible": true, //Since 1.7.2
"table.actions.visible": false //Since 1.7.2
}
sidebar.visibleproperty is used for displaying the left column of the search view.sidebar.actions.visibleproperty is used for displaying the actions in the left column of the search view.table.buttons.add.visibleproperty is used for displaying the Add button.table.buttons.delete.visibleproperty is used for displaying the Delete button when one or multiple rows are selected.table.actions.visibleproperty is used for displaying the actions when one or multiple rows are selected.
Edit View tabs
The edit view tabs displays one entity in a form tab, allowing the user to view or change the properties.
Localization
The localization system in Kodall provides a robust, dynamic, and multi-tenant translation mechanism for low-code applications. Instead of hardcoding user-facing strings (like titles, column headers, actions, inputs, menus, or dashboard items) directly in configurations, Kodall references localization keys. These keys are resolved to translated text at runtime based on the user's active locale.