|BatchSelection||When "True", BatchSelection allows the user to select a number of chart or table options and then click an "Update" or "OK" button to refresh the page.
Normally, when False, the charts and tables are updated as the user makes individual choices.
Setting BatchSelection="True" can speed the user interface by reducing the number of updates to the server.
Typically, you would compare values using a token, such as "@Data.value~ < 0" or "@Session.ShowCol1~=='true'". Elements are removed when the Condition evaluates to False.
Use quotes when working with strings:
"@Data.myColumn~" == "SomeValue"
If your data token may have a double quote inside of it, you should use single quotes:
'@Data.myColumn~' == 'SomeValue'
String valued data tokens with single and double quotes inside are not supported by the condition attribute.|
|ExcludeDetailRowsDefault||Users may group rows within the AnalysisGrid table. Normally, detail rows are included. In the table's configuration panel, a checkbox allows excluding detail rows. Setting this attribute to "True" causes detail rows to be initially hidden.
In some cases, especially when working with very large databases, performance is better without detail rows.
The default is "False".|
|HideAgAggr||Hide the "Aggregate" panel so that it is not available to the user.|
|HideAgFormat||Hide the "Format" column formatting options so they are not available to the user.|
|HideAgGroup||Hide the "Group" panel so that it is not available to the user.|
|HideAgLayout||Hide the layout ("Columns") panel so that it is not available to the user.|
|HideAgPaging||Hide the "Paging" panel so that it is not available to the user.
To hide the table paging controls, set the PageRowCount attribute to 0.|
|HideAgSortOrder||Hide the "Sort Order" panel so that it is not available to the user.|
|SecurityRightID||When entered, access to this element can be controlled with Logi security. Supply the ID of a right defined in the applications settings’ Security element. Only users that have a right in the SecurityRightID will be able to see the element.
Note that when rights come from RightFromRole elements under Security/UserRights, and this element's SecurityRightID does NOT match any of the Right IDs defined in the Settings definition, then the user DOES have access. But when Right IDs are instead derived from RightsFromDataLayer or RightsFromRoles elements, and the user DOES NOT have a matching Right, then the user DOES NOT have access.
You can enter multiple right IDs, separated by commas. In this case, the user sees the element if he has any one of the Rights.
|TemplateModifierFile||Some elements employ a definition file as a template. The definition contains language and culture specific Caption attributes that you may want to change. Or you may simply want to change the captions to better suit your application.
The TemplateModifierFile is an XML file with elements pointing to other elements in the template to be changed. All other attributes get applied in the template.
For example, the Dashboard2 element has a template file (rdTemplate\rdDashboard\rdDashboard2Template.lgx) several Label elements. One has an ID="lblAddPanelsTitle". The Caption can be changed with the following XML in the TemplateModifierFile:
You can set attributes for any number of elements. Examine the template file to learn the ID and Caption attributes you may want to modify.
The above example shows how to identify template elements with an ID attribute. Alternatively, you can also identify elements with an XPath expression. In this example, we change an attribute of the InteractivePaging element:
For a more detailed list of modifier actions see the following DevNet article.
TemplateModifierFiles can be in any folder accessable to the web application. When a directory location is not specified, the default location is the _SupportFiles folder.