Opening a Page with a Grid Component and Showing Selected Records
/documentation/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.
Grid Component - SQL Database Errors
/documentation/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:
Setting Dialog Control Properties
/documentation/pages/Server/Guide/Design/Data/FieldRules/Setting Dialog Control Properties.xml
Select each control in the Control Types list to display its Control Properties menu. There are many optional properties for each control. The default values for these properties produce a useable starting configuration for your dialog. This means that you can largely ignore these optional properties when you are learning to build dialogs or you expect to gradually refine your design in later revisions. A dialog component has few requirements. You are free to add and format controls (of any type) as you wish. The ((|#Data_Type|Data Type)) setting informs the page how to validate input to a control. It does not affect the type of data generated by a control, which is always "character" data.
Grid Component - Checkbox Column - Custom Ajax Callbacks
/documentation/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:
Record Navigator and Grid Toolbar
/documentation/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.
Custom Component Sections and Events
/documentation/pages/Guides/Mobile and Web Components/Custom/Custom Component Sections and Events.xml
Let's go over the Sections and Events of the Custom Component Builder.
Grid Component Builder - Setting Default Properties
/documentation/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.
Sharing and Using a Custom Component
/documentation/pages/Guides/Mobile and Web Components/Custom/Sharing and Using a Custom Component.xml
Once you have a working custom component, you can share it with others by sending them the .A5WCMP file that contains the component. They will need to copy it into their web project folder to use it. If your component uses Xbasic functions in an AEX file, or your component uses CSS or JavaScript files, you will need to supply those files as well.
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.
How to Test Page and Component Security
/documentation/pages/HowTo/Security/Testing Page Security.xml
If your application has web security enabled, you can verify that security settings are properly configured by publishing your application locally and logging in using user accounts configured with different permissions.