> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/super-filter/features/8.-variance.md).
# 8. Variance
{% hint style="success" %}
**Supported in: ❌**Date Filter **✔️**Facet Filter **✔️**Hierarchy Filter **❌**Alpha Numeric Filter
**❌**Numeric Filter
{% endhint %}
The **Variance** feature enables users to display **KPI Variance Cards** directly within the **Facet** and **Hierarchy Filter** as an icon in the user interface. This feature makes it easy to analyze and interpret data variances at a glance.
## Steps to configure Variance:
{% stepper %}
{% step %}
Add two measures to the **Other Field**. This will automatically enable the **Variance** section in the **Format Pane**, allowing you to configure variance using the first two measures added.
{% endstep %}
{% step %}
To customize variance settings, open the **Variance Config** section in the **Format Pane**. Select a measure from the dropdown to calculate variance based on the difference between the two measures.
{% endstep %}
{% step %}
Once the variance is calculated, a **variance icon** is added to the items in the category, providing a clear visual indicator.
{% endstep %}
{% step %}
By default, negative variance is displayed. To view only positive variance, enable the **Positive Variance** toggle.
{% endstep %}
{% step %}
Customize the colors for **positive and negative variances** using the color picker.
Image 1: Variance config in Format pane
{% endstep %}
{% step %}
The configured variance is displayed in the **Facet Filter** for each item within a category. However, in the **Hierarchy Filter**, variance is only shown for the leaf-level nodes within the hierarchy.
Image 2: Variance icon in Facet Filter
Image 3: Variance icon in Hierarchy Filter
{% endstep %}
{% endstepper %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.inforiver.com/super-filter/features/8.-variance.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
