Indigo DRS Data Reporting System Indigo DRS
Report Styles Indigo DRS Help

Report Styles are used to define fonts, colors, borders and the appearance of text and other elements in the Report.

Styles and are declared globally in the Report and can also be defined in a shared Report RDL File.

To add or edit Report Styles open the Report Styles Editor from the menu Design | Report Styles or select the Styles (...) collection button from the Report property page.

The Report Style will be available from the drop-down list for Style Name property when applied to Report Paragraphs, Tables and other elements.

Report RDL Files

Report Styles exported using the Export Wizard can also be reused as a shared Resource File by setting the File property of the Styles File to the exported or saved RDL content.

Click the Styles File (...) property button to specify the URI File or URI Query for shared Report Styles.

Styles File

The Styles File represents a list of shared Report Styles exported or saved as Report RDL elements which can be reused and shared between other Reports.

File URI's

Report File URI's are expressed as Uniform Resource Identifiers (URI) and can be either a Literal or a Query to specify the location of the File Resource. Literal values are constants that are determined by the URI File property.

Query based URI's are determined by the result of the URI Query which can be a series of XQuery or Python statements to specify the location of the File URI.

Report Rules

Report Rules are conditional XQuery or Python expressions that determine if Report content is enabled and applied to the build. Rule based queries return a Boolean that is either True or False and can query the Report Data Source and other Report Data Contexts. Rules are used for controlling the flow, visibility and activation of reporting content.

Report Rules if empty or null by default will always return True.

Report Namespaces

Report Namespaces are used for providing uniquely named elements and attributes and is a mechanism to avoid name conflicts by differentiating elements or attributes within an XML document that may have identical names, but different definitions. If the Report Data Source contains namespaces they can be applied to the XQuery Processor.