- Grid Component - SQL Database Errors
/pages/Server/Guide/Design/View/Grid/Grid Component/Grid Component SQL Database Errors.xml
You can now customize the text that is displayed when the SQL Database reports an Insert, Update or Delete error.
By default, Alpha Anywhere displays this text for an Update, Delete or Insert Error:
- Property-Grid Style Dialog
/pages/Guides/Desktop/Xdialog/Property-Grid Style Dialog.xml
To create a property-grid style Xdialog.
- Grid Component Search Part
/pages/Guides/Mobile and Web Components/Grid/The Search Part/Grid Component Search Part.xml
A guide to all of the options available in the grid component search part.
- How to Call a UX Component from a Grid and Pass Information from the UX Component Back into the Grid
/pages/HowTo/Grid/Calling a UX Component from a Grid and Pass Information from the Dialog Back to the Grid.xml
Steps and examples on how to do this are described in this page.
- Record Navigator and Grid Toolbar
/pages/Guides/Mobile and Web Components/Grid/Grid Properties/Record Navigator and Grid Toolbar/index.xml
The Record Navigator lets you design how users to move through the records shown in your application. It also lets you change the appearance of the navigation part of your grid. If you want your record navigator to take the form of a tree-control there is a section in the properties for this here. Included in the Record Navigator properties is the Help Window property. This will allow you to build Help for your application, check out this page to see more information on building a Help system.
- Grid Component - Checkbox Column - Custom Ajax Callbacks
/pages/Server/Guide/Design/View/Grid/Grid Component/Grid Component Checkbox Column, Custom Ajax Callbacks.xml
When you do a custom Ajax callback, the 'e' object that is passed into your Xbasic function that handles the callback contains a lot of useful information. Now, the 'e' object contains 3 additional properties that are automatically set if the grid has a checkbox column. The properties are:
- Grid Component Builder - Setting Default Properties
/pages/Server/Guide/Design/View/Grid/Grid Component/Grid Component Builder Setting Default Properties.xml
The Options, Set Default Properties command in the Grid Builder has always allowed you to set default properties for the Grid when you create a new Grid. However, if you created a new Grid from a Template, the default properties that you set were not honored. They were only honored if you created a blank new grid. Now, the default properties are used even if you use a template. This makes it much easier to customize the Grid builder for developers whose native language is not English.
- Opening a Page with a Grid Component and Showing Selected Records
/pages/Server/Guide/Design/View/Grid/Opening a Page with a Grid Component and Showing Selected Records.xml
A common requirement when building a grid is to have a hyperlink field in the grid that, when clicked, will open a second page. The second page contains a grid that is filtered based on parameters from the first page. These examples show how to do this.
The URL that opens the second page has query parameters that contain one or more of the _filter, _order, and _link keywords. These keywords allow you to specify a filter, order and/or linking parameters for the grid in the target page.
- Creating a Property Grid for a User-defined Component
/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.
- Passing a Record from a Grid to a Dialog
/pages/Server/Guide/Design/View/Grid/Passing a Record from a Grid to a Dialog.xml
Web publishing applications only. The problem is the following. You have selected a record in a grid and now want to display it in a separate page containing dialog component. The solution to the problem lies in the fact that you can set default values for a dialog component's variables in the URL of the page that loads the dialog.