|AllowControlHiding||When True, AllowControlHiding adds a button to the AnalysisChart that allows the user to collapse the chart controls.
The default is "False".|
|AnalysisChartTypes||A comma-delimited list of chart types available within the AnalysisChart.
Possible values are Pie, Bar, Line, Spline, Scatter, Heatmap and Gauge.
(A spline chart is a curved line chart.)
The first type listed will be the initial/starting chart type.
The Pie chart option only appears when there is at least one AnalysisChartColumn with DataType="Text". Bar charts require a Text or Date column.
|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.
|ChartHeight||The height of the chart image, in pixels.|
|ChartWidth||The width of the chart, usually in pixels.
For ChartCanvas charts, the value may be a percentage, by specifying the value like "50%".|
|Class||Sets the Cascading Style Sheet class used by the element. When set, this class will also be used by all child elements that don't have their own class. The class should be defined in the report's style sheet file. |
|Color||Sets the element's color. Enter a color by name, decimal RGB value, or hex RGB value. Prefix hex values with the pound sign, like #112233.
For bar charts, each bar can be a different color by entering multiple colors, each separated by a comma.
When using a Crosstab Filter under the Chart's DataLayer, use comma-separated colors and a Legend element so each crosstab set can be identified.|
|ControlPanelLocation||Sets the location of the elements controls.
The default is "Top".
"Left" is not recommended for MobileReport definitions.|
|ID||(Required) The ID attribute is a pervasive attribute that uniquely identifies an element within a definition file. The ID needs to be a unique value within the definition.|
|SaveFile||Specifies a file to save the end-user's changes for the current element. When the element is reloaded it is shown in the same state as when it was last used.
The file will be created if it does not exist. The containing folder is not automatically created. Ensure that the ASPNET process (Process Identity) has "write" access rights to the folder.
To have a different save file for each user, include the @Function.UserName~ token in part of the filename.
It's often useful to specify the folder in the Constants element in the settings definition file.
Do not set the SaveFile when using an AutoBookmark element.|
|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.