Skip to main content

Bookmark Tag Reference

info

The Bookmark Tag is used in conjunction with Link and EndLink Tags to create a link to another location in your Report Template's generated output.

For a step-by-step example of using a Bookmark Tag, see How Do I Use a Bookmark Tag?

For more details about Link and EndLink Tags, see Link and EndLink Tag Reference.

Bookmark Tag Properties​

Here we see the properties of a Bookmark Tag. Below, each property is described in detail. Unless otherwise noted, each property is required.

Tag Properties​

nickname (optional)

The nickname will appear in the template rather than the generic "bookmark" label. Square brackets ("[]") will surround any text you enter here when it appears in the template to identify it as a Tag. Descriptive nicknames can be very important in designing complex templates.

Standard Properties​

description (optional)

A brief description of this Tag.

enabled (default: on)

Controls whether a Tag is executed when generating output. This can be useful when debugging a template.

  • on- this Tag will be executed when output is generated.
  • off - this Tag will not be executed when output is generated.
  • engine-only - this Tag will be executed only if output is generated using one of the Report Engines.
  • autotag-only - this Tag will be executed only if output is generated using Report Designer.

Advanded Properties​

error-handling (optional)

Selects which types of errors produce warnings rather than exceptions, which allows output to be generated despite the error.

  • Ignore type error - these errors occur when a Tag's defined data type is different than the data type of the data returned by the Tag's query.
  • Ignore formatting error - these errors occur when a Tag's specified format is not compatible with the format of the data returned by the Tag's query.
  • Ignore select error - these errors occur when a Tag's query fails to find valid data.
  • Node must exist - these errors occur when a row or node is queried which doesn't exist in the data source. These errors typically return an empty value that is output without warning.
  • Node must not return NULL - these errors occur when a query returns an empty or NULL value. These errors typically return an empty value that is output without warning.
  • Treat warning as error - forces all of the above error-handling warnings to appear as errors (not exceptions). This is useful when used with Report Designer's Verify feature