If this element is defined the n the layout element containing it will be conditionally rendered based on the evaluation of the variable referenced. If the variable is of type boolean, then the renderFor is not required. The layout element will be rendered if the variable evaulates to this value. Defines a data source for a layout element. The data may be obtained from either a static value, the result of a query data item or the result of evaluating a layout expression. Contains a list of conditional data sources. When rendering, the variable pointed to by refVariable will be eveluated and the first conditionalDataSource whose refVariableValue matches the value of the expression will be used. If no match is found, dataSource of the parent element will be applied. An expression that is evaluated by the rendering engine at the current rendering context. Query data item references can be either qualified or un-qualified (e.g. [MasterQuery].[Column1] or [Column1]). Only un-qualified references are put into the result set definition. Allowable Expression Syntax in EBNF Report Expression that evaluates to true or false. Used in conditional styles and other similar elements. An boolean expression that is evaluated by the rendering engine at the current rendering context. Query data item references can be either qualified or un-qualified (e.g. [MasterQuery].[Column1] or [Column1]). Only un-qualified references are put into the result set definition. Allowable Expression Syntax in EBNF This element identifies the default measure to be used for a crosstab or chart. If the measures of the crosstab or chart cannot be determined by what is being rendered on the edges, then the default measure will be rendered. Defines a list of drills. Represents a drill action that is available for this layout element. Optionally identify the report that is the destination of the drill. If not specified, then the drill is within this report. The source context is optional to indicate that no value is being provided for the target parameter. If the target parameter is optional then no prompting should occur. When an OLAP entity is sourced as a parameter value for a drill through, the mapping of values to be passed to the target is rigid and arbitrary. Particularly when drilling from OLAP to relational, the mapping of a member to a column value may be unnecessarily restrictive, resultilng in greatly increased effort and complexity to work around the limitations. The "business key" attribute is used exclusively for drill through value mapping, which may not necessarily be the desired linkage for drill through. In order to support generalized drill through, particularly where the target parameter is used to perform linkages beyond the established rules for model conformance, it becomes necessary for the author to determine the most appropriate source member role. The mechanisms for establishing drill through parameter value associations needs to be extended in order to allow the selection of alternate attributes, besides the business key. Similarly, authoring of package based drill through objects needs to include the ability to select an arbitrary intrinsic attribute of an OLAP entity to be mapped to the more basic datatypes which may be encountered as target parameters. Indicates whether or not the report is launched in a new window. Indicates with what method the target report is to be accessed: - no method specified - the drill through target is launched according to the default action in the portal - method="edit" - the drill through target is launched with the editor appropriate for the object type in the object model - method="execute" - the drill through target is launched (and executed) in the report viewer - method="view" - the report output for the drill through target is viewed in the report viewer Specifies what format to produce or view. If missing, the format of the report from which the drill originates is used. If true then the dynamic filtering context is passed to the target report in a drill through. Defines which bookmark to jump to. Label which will appear if the user must choose between different report drills. Uniquely names the report drill in this report. Defines the master/detail linkages for the detail layout element that this is contained in. If there are no masterDetailLink defined, then the detail query is run unfiltered. Links a member set or parameter of the master query to a member set or parameter in the detail query. Identifies dataItems that will behave as properties of whichever layout element contains this list. A dataItem listed here will have data available at rendering time at this place in the layout context. A list of named conditional styles. Each of the style cases will be evaluated in the order they occur and the first one whose style condition evaluates to true will be applied. If none of the cases evaluates to true, then the style default will be used. Picks a style based on a range. The styleRanges must be ordered from largest to smallest. They will be evaluated in order to determine if the value is greater than (or equal to if inclusive) the current value. If true, then the style will be applied. If none of the styleRanges are applied, and the styleRangeRemaining isn't applied, then the styleDefault will be applied. The styleDefault will be applied for any missing values or any values where the conditionalDataItem isn't applicable. The value attribute must be in the following form for the different datatypes: date : YYYY-MM-DD datetime : YYYY-MM-DD HH:MM:SS.MMM time : HH:MM:SS.MMM interval : D HH:MM:SS.MMM ( this can also be negative). Picks a style based on equality with sets of values or defined ranges of values. The styleValueConditions will be evaluated in order to determine if the value is covered by them. If true, then the style will be applied. If none of them are applied, then the styleDefault will be applied. rn_internal_4.0 List of references to named conditional styles. Reference to a data item and query from a conditional style or conditional palette. Drop shadow that is rendered around containers. The offset attributes are measured in pixels and can be negative. Gradient that can be applied to the entire page. It will resize when the browser is resized, unlike the generatedBackground gradient. Describes the suppress applied to the list element. Describes the suppress applied to the crosstab element. Describes the suppress applied to the chart element. Represents the value of the specificied data item that is available in the current layout context. Represent the label of the data item specifiied. The label is available in the result set. Represents the caption of the current member context being rendered in the layout. This element is only allowed within a crosstabs or charts where edge members are rendered. Represents the value of the current cell context being rendered in the layout. This element is only for crosstabs or charts where the cell values are rendered. Represents the value of the specificied static data item that is available in the current layout context. Specifies the target attribute of the hyperlink. For buttons, the code for the onClick tries to simulate what the target attribute of an anchor tag would do. Any layout element may be given a name. The name must be unique for all layout elements in the report. It is primarily allow a layout element to be referenced as a component (layoutComponentRef). Renders all headers on same page as first N detail rows, where 'N' is the given numeric value. If not specified then a page break may occur between headers and their associated detail rows. Renders all footers on same page as last N detail rows, where 'N' is the given numeric value. If not specified then a page break may occur between footers and their associated detail rows. Renders this element with the N next elements on the edge, where 'N' is the given numeric value. If not specified then a page break may occur between this element and the next element on the edge. Renders this element with the N previous elements on the edge, where 'N' is the given numeric value. If not specified then a page break may occur between this element and the previous element on the edge. If this attribute is specified, then whenever this layout element is rendered, the current page number for the rendering will be reset to the indicated value. If this attribute is specified, then whenever this layout element is rendered, the current page count for the rendering will be reset to the indicated value. Controls repetitive rendering of this object on each page. When the frame contains more columns than can be rendered on a given page, an overflow (or "fault right") occurs. When the frame contains more rows than can be rendered on a given page, an page break (or "fault down") occurs. When 'true', this object will be rendered on the next or overflow page. Any element that has these attributes can act as a global singleton. All elements in the layout that reference same query and have singleton="true" would share the same result set, the row cursor would never be moved pass row 1. All elements in the layout (not including frames) that reference the same query and have singleton="false" would use the resultset of the closest parent frame that references that query, the row context in this case is clear. If no parent frame can be found, then no value will be rendered. This attribute indicates that the footer element is to be pushed to the bottom of the rendering. The last instance of the footer element rendered on this page will be the one pushed to the bottom. [DEPRECATED] The solveOrder attribute should now be specified on the dataItem. Specifies the solve order for this calculation. If no solve order is specified then the solve order will be follow the default rules that the server uses to determine solve order. Specifies whether this element will do horizontal pagination. If this attribute is set to true then the page will be rendered when no data contents are generated Provides a text alternative for the image based element. This is primarily used to provide accessibility in a report.