Chart Linked Settings - Revision history

Ollvihe: /* Dashboard variables */

2026-02-22T15:35:24Z

Dashboard variables

@@ Line 164: / Line 164: @@
 			"type": "generic",
 			"parameter": "maxRows"
+		}
+	]

Ollvihe: /* Configuration */

2026-02-22T15:33:06Z

Configuration

← Older revision		Revision as of 15:33, 22 February 2026
Line 27:		Line 27:
	* '''tagName''': When ''type'' is ''tag'', defines the bound tag name. The tag can be used in custom expressions similar to variables with syntax <#MyTagName>. Linking to tags is one-way: when a setting is changed, the tag is changed accordingly. On the other hand, the tag value itself cannot be changed directly.		* '''tagName''': When ''type'' is ''tag'', defines the bound tag name. The tag can be used in custom expressions similar to variables with syntax <#MyTagName>. Linking to tags is one-way: when a setting is changed, the tag is changed accordingly. On the other hand, the tag value itself cannot be changed directly.
	* '''variableName''': When linked setting type is ''variable'', defines the dashboard variable name. Mandatory when the linked setting type is ''variable''. Linking to variables is two-way: when a variable value is changed, the other linked setting is changed accordingly, and when the other setting is changed, a linked variable value is changed accordingly.		* '''variableName''': When linked setting type is ''variable'', defines the dashboard variable name. Mandatory when the linked setting type is ''variable''. Linking to variables is two-way: when a variable value is changed, the other linked setting is changed accordingly, and when the other setting is changed, a linked variable value is changed accordingly.
	** If the variable ~~name~~ contains ~~at least one dot (".")~~, the variable name ~~is assumed to be a json~~ path ~~where the~~ part before the first dot is the actual dashboard variable name and the rest define the ~~json~~ path. Example: Variable name in linked setting: "Filter.Perspective.ObjectType", variable value: "Orders" --> created dashboard variable name: "Filter", value: { "Perspective": {"ObjectType": "Orders" } }.		** If the dashboard variable contains JSON data, it's possible to refer to a specific property in the JSON, with following syntax '''<variable name>.<JSON path>'''. The part before the first dot is the actual dashboard variable name and the rest define the JSON path. Example: Variable name in linked setting: "Filter.Perspective.ObjectType", variable value: "Orders" --> created dashboard variable name: "Filter", value: { "Perspective": {"ObjectType": "Orders" } }.
	* '''variableFormat''': Defines whether the linked variables use the '''stringified''' (default) ([[Stringified Value Format\|more about stringified value format]]) or '''json''' format (https://en.wikipedia.org/wiki/JSON).		* '''variableFormat''': Defines whether the linked variables use the '''stringified''' (default) ([[Stringified Value Format\|more about stringified value format]]) or '''json''' format (https://en.wikipedia.org/wiki/JSON).
	** When working with Snowflake models, use the ''stringified'' format.		** When working with Snowflake models, use the ''stringified'' format.

Ollvihe: /* Configuration */

2026-02-20T20:05:59Z

Configuration

← Older revision		Revision as of 20:05, 20 February 2026
Line 20:		Line 20:
	** '''variable''': For binding to a dashboard variable. Dashboard variables can be used to bind together settings across multiple charts. Linked settings need to be defined for all the bound charts.		** '''variable''': For binding to a dashboard variable. Dashboard variables can be used to bind together settings across multiple charts. Linked settings need to be defined for all the bound charts.
	** '''tag''': For binding to a tag. Tags can be used in the custom expressions.		** '''tag''': For binding to a tag. Tags can be used in the custom expressions.
	** '''onscreensetting''': For binding to a value of an on-screen setting in the same chart. The specific on-screen setting can be referred to by ''index'' or ''parameter'' (see below).		** '''onscreensetting''': For binding to a value of an [[Chart_On-screen_Settings\|on-screen setting]] in the same chart. The specific on-screen setting can be referred to by ''index'' or ''parameter'' (see below).
	** '''filtervalue''': For binding to filter rule parameters, such as case/event attribute values or event types.		** '''filtervalue''': For binding to filter rule parameters, such as case/event attribute values or event types.
	** '''filterattribute''': For binding to case or event attribute name in CaseAttribute, EventAttribute, and Attribute filter rule types.		** '''filterattribute''': For binding to case or event attribute name in CaseAttribute, EventAttribute, and Attribute filter rule types.

Ollvihe: /* Binding to case attribute filters with attribute name and attribute values */

2026-02-20T20:05:30Z

Binding to case attribute filters with attribute name and attribute values

@@ Line 185: / Line 185: @@
+	]
+]
 </syntaxhighlight>

Ollvihe: /* Configuration */

2026-02-20T19:56:20Z

Configuration

← Older revision		Revision as of 19:56, 20 February 2026
Line 18:		Line 18:
	** '''root''': For analyzed objects parameters.		** '''root''': For analyzed objects parameters.
	** '''generic''': For other settings in the chart, such as ''Maximum rows'' (technical name: maxRows), ''Visualization'' (technical name: maxRows), ''Show Data Labels'' (technical name: datalabels), ''Model'' (technical name: modelId), etc.		** '''generic''': For other settings in the chart, such as ''Maximum rows'' (technical name: maxRows), ''Visualization'' (technical name: maxRows), ''Show Data Labels'' (technical name: datalabels), ''Model'' (technical name: modelId), etc.
			** '''variable''': For binding to a dashboard variable. Dashboard variables can be used to bind together settings across multiple charts. Linked settings need to be defined for all the bound charts.
	** '''tag''': For binding to a tag. Tags can be used in the custom expressions.		** '''tag''': For binding to a tag. Tags can be used in the custom expressions.
	** '''~~variable~~''': For binding to a ~~dashboard variable~~. ~~Dashboard variables~~ can be ~~used~~ to ~~bind together settings across multiple charts. Linked settings need to be defined for all the bound charts~~.		** '''onscreensetting''': For binding to a value of an on-screen setting in the same chart. The specific on-screen setting can be referred to by ''index'' or ''parameter'' (see below).
	** '''filtervalue''': For binding to filter rule parameters, such as case/event attribute values or event types.		** '''filtervalue''': For binding to filter rule parameters, such as case/event attribute values or event types.
	** '''filterattribute''': For binding to case or event attribute name in CaseAttribute, EventAttribute, and Attribute filter rule types.		** '''filterattribute''': For binding to case or event attribute name in CaseAttribute, EventAttribute, and Attribute filter rule types.
	** '''onscreensetting''': For binding to a value of an on-screen setting in the same chart. The specific on-screen setting can be referred to by ''index'' or ''parameter'' (see below).
	* '''index''': Defines the order number (starts from 0). Used when ''type'' is a ''measure'', ''dimension'', ''eventtypemeasure'', ''flowmeasure'', ''filtervalue'', or ''onscreensetting''.		* '''index''': Defines the order number (starts from 0). Used when ''type'' is a ''measure'', ''dimension'', ''eventtypemeasure'', ''flowmeasure'', ''filtervalue'', or ''onscreensetting''.
	* '''parameter''': Name of the chart setting or parameter. All properties stored to the ''expressionParameters'' in chart json settings, can be used. In addition, following property names are available: "aggregate", "decimals", "unit" and "dateGranularity".		* '''parameter''': Name of the chart setting or parameter. All properties stored to the ''expressionParameters'' in chart json settings, can be used. In addition, following property names are available: "aggregate", "decimals", "unit" and "dateGranularity".

TeeHiet: TK-61458

2026-02-03T09:53:20Z

TK-61458

← Older revision		Revision as of 09:53, 3 February 2026
Line 21:		Line 21:
	** '''variable''': For binding to a dashboard variable. Dashboard variables can be used to bind together settings across multiple charts. Linked settings need to be defined for all the bound charts.		** '''variable''': For binding to a dashboard variable. Dashboard variables can be used to bind together settings across multiple charts. Linked settings need to be defined for all the bound charts.
	** '''filtervalue''': For binding to filter rule parameters, such as case/event attribute values or event types.		** '''filtervalue''': For binding to filter rule parameters, such as case/event attribute values or event types.
	** '''filterattribute''': For binding to case or event attribute name in filter rule.		** '''filterattribute''': For binding to case or event attribute name in CaseAttribute, EventAttribute, and Attribute filter rule types.
	** '''onscreensetting''': For binding to a value of an on-screen setting in the same chart. The specific on-screen setting can be referred to by ''index'' or ''parameter'' (see below).		** '''onscreensetting''': For binding to a value of an on-screen setting in the same chart. The specific on-screen setting can be referred to by ''index'' or ''parameter'' (see below).
	* '''index''': Defines the order number (starts from 0). Used when ''type'' is a ''measure'', ''dimension'', ''eventtypemeasure'', ''flowmeasure'', ''filtervalue'', or ''onscreensetting''.		* '''index''': Defines the order number (starts from 0). Used when ''type'' is a ''measure'', ''dimension'', ''eventtypemeasure'', ''flowmeasure'', ''filtervalue'', or ''onscreensetting''.
	* '''parameter''': Name of the chart setting or parameter. All properties stored to the ''expressionParameters'' in chart json settings, can be used. In addition, following property names are available: "aggregate", "decimals", "unit" and "dateGranularity".		* '''parameter''': Name of the chart setting or parameter. All properties stored to the ''expressionParameters'' in chart json settings, can be used. In addition, following property names are available: "aggregate", "decimals", "unit" and "dateGranularity".
	* '''tagName''': When ''type'' is ''tag'', defines the bound tag name. The tag can be used in custom expressions similar to variables with syntax <#MyTagName>. Linking to tags is one-way: when a setting is changed, the tag is changed accordingly. On the other hand, the tag value itself cannot be changed directly.		* '''tagName''': When ''type'' is ''tag'', defines the bound tag name. The tag can be used in custom expressions similar to variables with syntax <#MyTagName>. Linking to tags is one-way: when a setting is changed, the tag is changed accordingly. On the other hand, the tag value itself cannot be changed directly.
	* '''variableName''': When linked setting type is ''variable'', defines the variable name. Linking to variables is two-way: when a variable value is changed, the other linked setting is changed accordingly, and when the other setting is changed, a linked variable value is changed accordingly.		* '''variableName''': When linked setting type is ''variable'', defines the dashboard variable name. Mandatory when the linked setting type is ''variable''. Linking to variables is two-way: when a variable value is changed, the other linked setting is changed accordingly, and when the other setting is changed, a linked variable value is changed accordingly.
	* '''variableFormat''': Defines whether the linked variables use the '''stringified''' (default) ([[Stringified Value Format\|more about stringified value format]]) or '''json''' format (https://en.wikipedia.org/wiki/JSON). When working with Snowflake models, use the ''stringified'' format. The ''json'' format is required when using in-memory models with the [[Dropdown List Selector]] because for in-memory models, the Dropdown List Selector uses the ''json'' format (due to backward compatibility).		** If the variable name contains at least one dot ("."), the variable name is assumed to be a json path where the part before the first dot is the actual dashboard variable name and the rest define the json path. Example: Variable name in linked setting: "Filter.Perspective.ObjectType", variable value: "Orders" --> created dashboard variable name: "Filter", value: { "Perspective": {"ObjectType": "Orders" } }.
			* '''variableFormat''': Defines whether the linked variables use the '''stringified''' (default) ([[Stringified Value Format\|more about stringified value format]]) or '''json''' format (https://en.wikipedia.org/wiki/JSON).
			** When working with Snowflake models, use the ''stringified'' format.
			** The ''json'' format is required when using in-memory models with the [[Dropdown List Selector]] because for in-memory models, the Dropdown List Selector uses the ''json'' format (due to backward compatibility). When using ''json'' format, date values are encoded as strings with the following format: yyyy-MM-ddTHH:mm:ss.fff.
			** If the variable name is one of the listed below, no formatting is used in the variable value (i.e., the variableFormat parameter is ignored):
			*** sys:dashboard
			*** sys:language
			*** sys:dateFormat
			*** sys:firstDayOfWeek
			*** sys:use12HourClock
			*** sys:hideViewHeader
			*** ModelId
			*** FilterId
			*** Filter
			*** DashboardFilter
			*** FilterSelection
			*** Comparison
			*** designModel
			*** SelectedPresentationObject
	* '''filterGroupType''': When ''type'' is ''filtervalue'' or ''filterattribute'', defines the filter group type as one of the following: ''IncludeCases'', ''ExcludeCases'', ''IncludeEvents'', ''ExcludeEvents'', ''IncludeEventTypes'', ''ExcludeEventTypes''. Mandatory.		* '''filterGroupType''': When ''type'' is ''filtervalue'' or ''filterattribute'', defines the filter group type as one of the following: ''IncludeCases'', ''ExcludeCases'', ''IncludeEvents'', ''ExcludeEvents'', ''IncludeEventTypes'', ''ExcludeEventTypes''. Mandatory.
	* '''filterRuleType''': When ''type'' is ''filtervalue'' or ''filterattribute'', defines the filter rule type as one of the following: ''CaseAttributeValue'', ''EventAttributeValue'', ''Attribute'', ''EventType'', ''Case''. Mandatory.		* '''filterRuleType''': When ''type'' is ''filtervalue'' or ''filterattribute'', defines the filter rule type as one of the following: ''CaseAttributeValue'', ''EventAttributeValue'', ''Attribute'', ''EventType'', ''Case''. Mandatory.

TeeHiet: TK-60700

2026-01-27T13:35:14Z

TK-60700

← Older revision		Revision as of 13:35, 27 January 2026
Line 28:		Line 28:
	* '''variableName''': When linked setting type is ''variable'', defines the variable name. Linking to variables is two-way: when a variable value is changed, the other linked setting is changed accordingly, and when the other setting is changed, a linked variable value is changed accordingly.		* '''variableName''': When linked setting type is ''variable'', defines the variable name. Linking to variables is two-way: when a variable value is changed, the other linked setting is changed accordingly, and when the other setting is changed, a linked variable value is changed accordingly.
	* '''variableFormat''': Defines whether the linked variables use the '''stringified''' (default) ([[Stringified Value Format\|more about stringified value format]]) or '''json''' format (https://en.wikipedia.org/wiki/JSON). When working with Snowflake models, use the ''stringified'' format. The ''json'' format is required when using in-memory models with the [[Dropdown List Selector]] because for in-memory models, the Dropdown List Selector uses the ''json'' format (due to backward compatibility).		* '''variableFormat''': Defines whether the linked variables use the '''stringified''' (default) ([[Stringified Value Format\|more about stringified value format]]) or '''json''' format (https://en.wikipedia.org/wiki/JSON). When working with Snowflake models, use the ''stringified'' format. The ''json'' format is required when using in-memory models with the [[Dropdown List Selector]] because for in-memory models, the Dropdown List Selector uses the ''json'' format (due to backward compatibility).
	* '''filterGroupType''': When ''type'' is ''filtervalue'' or ''filterattribute'', defines the filter group type as one of the following: ''IncludeCases'', ''ExcludeCases'', ''IncludeEvents'', ''ExcludeEvents'', ''IncludeEventTypes'', ''ExcludeEventTypes''.		* '''filterGroupType''': When ''type'' is ''filtervalue'' or ''filterattribute'', defines the filter group type as one of the following: ''IncludeCases'', ''ExcludeCases'', ''IncludeEvents'', ''ExcludeEvents'', ''IncludeEventTypes'', ''ExcludeEventTypes''. Mandatory.
	* '''filterRuleType''': When ''type'' is ''filtervalue'' or ''filterattribute'', defines the filter rule type as one of the following: ''CaseAttributeValue'', ''EventAttributeValue'', ''Attribute'', ''EventType'', ''Case''.		* '''filterRuleType''': When ''type'' is ''filtervalue'' or ''filterattribute'', defines the filter rule type as one of the following: ''CaseAttributeValue'', ''EventAttributeValue'', ''Attribute'', ''EventType'', ''Case''. Mandatory.
	* '''attribute''': When ''type'' is ''filtervalue'', defines the attribute name. Used for filter rule types ''CaseAttribute'', ''EventAttribute'' and ''Attribute''. This setting is optional, and when not defined, the linked setting is bound to the first filter rule matching with the ''filterGroupType'' and ''filterRuleType''.		* '''attribute''': When ''type'' is ''filtervalue'', defines the attribute name. Used for filter rule types ''CaseAttribute'', ''EventAttribute'' and ''Attribute''. This setting is optional, and when not defined, the linked setting is bound to the first filter rule matching with the ''filterGroupType'' and ''filterRuleType''.
	* '''expressionCategory''': When ''type'' is ''filtervalue'' or ''filterattribute'', and referring to a measure/dimension/column level filter, defines the measure/dimension/colum as one of the following: ''measure'', ''dimension'', ''eventtypemeasure'', ''flowmeasure''. When the expressionCategory is not defined, the linked setting refers to a chart level filter rule.		* '''expressionCategory''': When ''type'' is ''filtervalue'' or ''filterattribute'', and referring to a measure/dimension/column level filter, defines the measure/dimension/colum as one of the following: ''measure'', ''dimension'', ''eventtypemeasure'', ''flowmeasure''. When the expressionCategory is not defined, the linked setting refers to a chart level filter rule.

TeeHiet: TK-60700

2026-01-27T13:24:05Z

TK-60700

← Older revision		Revision as of 13:24, 27 January 2026
Line 22:		Line 22:
	** '''filtervalue''': For binding to filter rule parameters, such as case/event attribute values or event types.		** '''filtervalue''': For binding to filter rule parameters, such as case/event attribute values or event types.
	** '''filterattribute''': For binding to case or event attribute name in filter rule.		** '''filterattribute''': For binding to case or event attribute name in filter rule.
	* '''index''': Defines the order number (starts from 0). Used ~~hen~~ ''type'' is a ''measure'', ''dimension'', ''eventtypemeasure'', ''flowmeasure'', or ''~~filtervalue~~''.		** '''onscreensetting''': For binding to a value of an on-screen setting in the same chart. The specific on-screen setting can be referred to by ''index'' or ''parameter'' (see below).
			* '''index''': Defines the order number (starts from 0). Used when ''type'' is a ''measure'', ''dimension'', ''eventtypemeasure'', ''flowmeasure'', ''filtervalue'', or ''onscreensetting''.
	* '''parameter''': Name of the chart setting or parameter. All properties stored to the ''expressionParameters'' in chart json settings, can be used. In addition, following property names are available: "aggregate", "decimals", "unit" and "dateGranularity".		* '''parameter''': Name of the chart setting or parameter. All properties stored to the ''expressionParameters'' in chart json settings, can be used. In addition, following property names are available: "aggregate", "decimals", "unit" and "dateGranularity".
	* '''tagName''': When ''type'' is ''tag'', defines the bound tag name. The tag can be used in custom expressions similar to variables with syntax <#MyTagName>. Linking to tags is one-way: when a setting is changed, the tag is changed accordingly. On the other hand, the tag value itself cannot be changed directly.		* '''tagName''': When ''type'' is ''tag'', defines the bound tag name. The tag can be used in custom expressions similar to variables with syntax <#MyTagName>. Linking to tags is one-way: when a setting is changed, the tag is changed accordingly. On the other hand, the tag value itself cannot be changed directly.

Jaakko.knuutinen: Added an example Linked settings to filter events based on event attribute values.

2025-01-10T13:08:55Z

Added an example Linked settings to filter events based on event attribute values.

@@ Line 192: / Line 192: @@
 			"filterGroupType": "IncludeCases",
 			"filterRuleType": "CaseAttributeValue"
+		}
+	]
+]
 </syntaxhighlight>

Ollvihe: /* Binding to case attribute filters with attribute name and attribute values */

2024-01-07T19:10:14Z

Binding to case attribute filters with attribute name and attribute values

← Older revision		Revision as of 19:10, 7 January 2024
Line 169:		Line 169:

	=== Binding to case attribute filters with attribute name and attribute values ===		=== Binding to case attribute filters with attribute name and attribute values ===
	This example binds dashboard ~~variable~~ ''CaseAttributeName'' to the chart filter rule to include case attribute values~~, and variable ''CaseAttributeValues'' to the attribute values of the same filter rule~~. The filter rule need to pre-exist for these linked settings to work.		This example binds dashboard variables ''CaseAttributeName'' and ''CaseAttributeValues'' to the chart filter rule to include case attribute values. The filter rule need to pre-exist for these linked settings to work.
	<syntaxhighlight lang="json" line>		<syntaxhighlight lang="json" line>
	[		[