Important This space contains documentation for TrueSight Smart Reporting for Server Automation 20.02.01. For earlier releases, see TrueSight Smart Reporting for Sever Automation 19.2.

Using custom properties in reports

Core objects have several properties that are shipped with TrueSight Server Automation. You can create custom properties for these objects in TrueSight Server Automation and mark these properties for inclusion in reports. During the extract, transform, and load (ETL) process, these properties are added to the TrueSight Server Automation - Data Warehouse and can be used in the reports.  TrueSight Server Automation - Data Warehouse supports custom properties added for the following objects:

  • role
  • user
  • job
  • template
  • server
  • component

Each property definition in the dictionary includes the Used in reports field. By default, for the built-in properties to be displayed in reports, the Used in reports field is selected. When you add a new property to the dictionary, the Used in reports field is not selected by default. To include the new property in reports, select the Used in reports field for the property. The next time the ETL process synchronizes the custom properties, it includes any new properties for which Used in reports is selected.

If a property is deprecated or the Used in reports field is not selected for an existing property, the property is displayed in the reports, but when you drag and drop that property field to the report, it fails. Do the following:

  1. Click Update Content in TrueSight Smart Reporting - Platform to get all the updated properties from the data warehouse tables.
  2. Remove the properties from the report definition.

For information about the property dictionary, see Managing properties using the Property Dictionaryin the TrueSight Server Automation documentation.

Note: Using the same property in multiple sites and length constraints

  • The number of reports data warehouse properties is limited to 1,000 for each of the supported object types.
  • The EnableLongPropertyName flag affects only the server property.
  • If a property name exceeds 30 characters, use one of the following settings to update the system_property table in the TSSADW_DW database:
    • Set EnableLongPropertyName to true. With this setting, the property name after 30 characters is trimmed, but the property is loaded without any impact on the property value.
    • Set EnableLongPropertyName to false. With this setting, the property name that exceeds 30 characters is not loaded.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*