Power Search for Grid using a Dialog Component
/documentation/pages/Server/Guide/Design/View/Grid/Power Search for Grid using a Dialog Component.xml
Requires the Dialog Component - Power Search for an Embedded Grid Component feature pack, included in subscription
Filtering a Grid with a UX Component
/documentation/pages/Guides/Mobile and Web Components/Grid/Introducing the Grid Builder/Tutorials/Filtering/Filtering a Grid with a Dialog.xml
One of the most common tasks a web application can perform is to collect the values of one or more variables, then use this data to display a filtered view of a table.
Grid Component Properties and Methods
/documentation/pages/Ref/Client_Api/Grid/index.xml
Properties and methods that can be used on the client side to automate grid components.
Automatically Populating Linking Field Values when Doing Data Entry
/documentation/pages/Guides/Desktop/Design/Data/FieldRules/Automatically Populating Linking Field Values when Doing Data Entry.xml
The following scenario describes a situation in which you want to automatically populate "linking" fields in a grid component menus. Assume that you have an application with the following characteristics:
Creating a Property Grid for a User-defined Component
/documentation/pages/Guides/Mobile and Web Components/Custom/Creating a Property Grid for a User-defined Component.xml
One way to create a Property Grid for a User-defined Component is to use the Property Grid builder in Action Scripting to generate the markup. This is invoked by creating a New Script (using Action Scripting), adding a new action, and selecting Xdialog Windows|Display an Xdialog Box.
How to Use Custom Controls in a Grid Component
/documentation/pages/HowTo/Grid/Using Custom Controls in a Grid Component.xml
This topic discusses an advanced use of a Custom Control in a Grid component.
Overriding GridLinker Component Settings
/documentation/pages/Obsolete/Grid Linker Component/Overriding GridLinker Component Settings.xml
Overriding settings a GridLinker component at run-time is not as simple as it is for a grid or dialog component. This is because a lot of the code that executes is hidden inside the definition of the GridLinker component. Nevertheless, once you understand more about what goes on inside the GridLinker component, it is not hard to do. The first step is to make sure you know what the aliases are for each of the grid components in the GridLinker. To find the names of the aliases:
Entering and Changing Records
/documentation/pages/Guides/Desktop/Design/Data/DBF/Entering and Changing Records.xml
You can enter or change records in any open table (assuming the table is not write-protected or being used exclusively by another user or session). Several open tables or related tables from a set can be in Enter or Change mode simultaneously. To enter a new record into a table, you do the following:
UX and Grid Component - Javascript Confirmation Windows - Title Direction
/documentation/pages/Guides/Mobile and Web Components/UX/Code/Javascript In UX Components/Javascript Confirmation Windows - Title Direction.xml
By default, all confirmation dialogs show the title on the left and the close icon on the right. For right to left languages, you might want to change this. To do so, put the following Javascript in the Grid or UX onRenderComplete client-side event:
Open a AppLauncher component
/documentation/pages/Ref/Action Javascript/Open a AppLauncher component.xml
Open a AppLauncher component in a pop-up window, or in a DIV on the current page.