- 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
- TGRDL_CUST Tabbed GridLinker Component
/documentation/pages/Obsolete/Alpha Sports/Components/TGRDL_CUST Tabbed GridLinker Component.xml
Reviews and edits customer records and customer sales history.
- Owner Draw O Directive Command Summary
/documentation/pages/Guides/Desktop/Xdialog/Owner Draw O Directive Command Summary.xml
The following table summarizes all of the owner-draw string commands:
- Suppress summary section
/documentation/pages/Guides/Mobile and Web Components/Grid/Grid Properties/Summary value options/Suppress summary section.xml
Defines whether or not the summary section is shown in the Grid.
- Grid Component Properties and Methods
Properties and methods that can be used on the client side to automate grid components.
- 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.
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.
- 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:
- 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.