Configure Visualize This

Atoti Intelligence Essentials

This is part of the Atoti Intelligence Essentials offer.

Providing context about your cubes improves Visualize This responses: the more the LLM knows about the business meaning of cubes, dimensions, hierarchies, levels, and measures, the more relevant the visualizations it produces. Configuration is optional but recommended.

Prerequisites

Visualize This must be enabled before adding configuration. See Set up Visualize This in Java or Set up Visualize This in Python for setup instructions.

Atoti Java SDK

Add Visualize This configuration to the application configuration file. Add the following to application.yaml:

atoti:
  ai:
    cubes:
      - name: "cubeName1"
        description: "Description of the cube 1"
        dimensions:
          - name: "dimensionName1"
            description: "description dimension1"
            hierarchies:
              - name: "hierarchyName1"
                description: "description hierarchy1"
                levels:
                  - name: "levelName1"
                    description: "description level1"
          - name: "dimensionName2"
            description: "description dimension2"
            hierarchies:
              - name: "hierarchyName2"
                description: "description hierarchy2"
        measures:
          - name: "measure1"
            description: "description measure1"
          - name: "measure2"
            description: "description measure2"
        measure-folders:
          - name: "folderName1"
            description: "description folder1"
          - name: "folderName2"
            description: "description folder2"
      - name: "cubeName2"
        description: "Description of the cube 2"
        dimensions:
          - name: "dimensionName3"
            hierarchies:
              - name: "hierarchyName3"
                levels:
                  - name: "levelName3"
                    description: "description level3"
              - name: "hierarchyName4"
                description: "description hierarchy4"
                levels:
                  - name: "levelName4"
                    description: "description level4"
          - name: "dimensionName5"
            description: "description dimension4"
        measures:
          - name: "measure3"
            description: "description measure3"
          - name: "measure4"
            description: "description measure4"
        measure-folders:
          - name: "folderName3"
            description: "description folder3"
          - name: "folderName4"
            description: "description folder4"
    system-prompt-paths:
      - "prompts/prompt1.md"
      - "prompts/prompt2.md"

Configuration parameters

The following table describes each configuration parameter:

Parameter name	Description
system-prompt-paths	Ordered list of paths to system prompt files. Files are concatenated in the declared order and appended to the LLM context.
name	Name of the cube to configure Visualize This for.
description	Description of the cube.
dimensions	List of dimensions to provide additional information to the LLM.
name	Name of the dimension.
description	Description of the dimension.
hierarchies	List of hierarchies to provide additional information to the LLM.
name	Name of the hierarchy.
description	Description of the hierarchy.
levels	List of levels to provide additional information to the LLM.
name	Name of the level.
description	Description of the level.
measures	List of measures to provide additional information to the LLM.
name	Name of the measure.
description	Description of the measure.
measure-folders	List of measure folders to provide additional information to the LLM.
name	Name of the measure folder.
description	Description of the measure folder.

Alternative: XMLA_DESCRIPTION property

Descriptions for dimensions, hierarchies, and levels can also be sourced from the XMLA_DESCRIPTION property set directly on the OLAP element schema definition. When this property is present on an element, Visualize This reads it as the element’s description. This is useful when descriptions are already defined in the cube schema, and you want to avoid duplicating them in the application configuration file. If both XMLA_DESCRIPTION and the application configuration file provide a description for the same element, the two values are concatenated.

The XMLA_DESCRIPTION property applies to dimensions, hierarchies, levels, and measures only. Cubes and measure folders must be described through the application configuration file.

Partial configuration

Configuration does not require descriptions for all elements. Provide descriptions only for elements that need additional context.

How to disable the chat endpoint

In a deployment with several applications, only one of them should serve chat: the main application that users send their prompts to. Disable the chat endpoint on every other application, and connect them to the main application over MCP. See How to configure chat across a deployment. An application can serve Atoti Intelligence without serving chat. Setting atoti.ai.chat.enabled to false, available from Atoti 6.1.25, registers no chat endpoint:

atoti:
  ai:
    chat:
      enabled: false

The chat endpoints are then absent, and every call to them answers 404 Not Found. The Atoti UI reports chat as absent, and shows no chat panel. The activeviam/ai namespace stays advertised on the /versions endpoint as long as Auto-Explain is enabled, since both features share it. Every other Atoti Intelligence feature keeps working, Auto-Explain and the MCP Server included. The setting defaults to true.

Turning chat off differs from configuring no LLM. An application with no LLM still registers the chat endpoints, which refuse each call with 404 Not Found until an LLM is configured. Chat there is absent only for as long as no LLM is.

In the Atoti Python SDK, set AiConfig.chat_enabled to False:

import atoti as tt
from atoti_ai import AiConfig

with tt.experimental({"ai"}):
    ai_config = AiConfig(chat_enabled=False)

session_config = tt.SessionConfig(ai=ai_config)

A session started that way serves no chat, and Session.chat reports chat as absent.

Dynamic tool discovery

Visualize This can send the LLM every available tool on each request. Alternatively, it can send only the tools that match the current request. Dynamic tool discovery is the second mode: the model calls a tool search tool that queries a keyword index and receives only the matching tools. This reduces prompt token usage and improves tool selection. Atoti enables dynamic tool discovery by default.

Dynamic tool discovery applies to both SDKs, and both can turn it off.

How to opt out

Turning dynamic tool discovery off sends the whole tool set to the model on every request instead. This restores the behavior Atoti used before dynamic tool discovery existed. A small tool set, where search adds no benefit, is one reason to turn it off. Debugging which tools the model can see is another. In the Atoti Java SDK, set spring.ai.chat.client.tool-search-advisor.enabled to false:

spring:
  ai:
    chat:
      client:
        tool-search-advisor:
          enabled: false

In the Atoti Python SDK, set AiConfig.dynamic_tool_discovery to False:

import atoti as tt
from atoti_ai import AiConfig

with tt.experimental({"ai"}):
    ai_config = AiConfig(dynamic_tool_discovery=False)

session_config = tt.SessionConfig(ai=ai_config)

Atoti Python SDK

The chat is available on the session through Session.chat. Its system_prompt is a custom addition to Atoti’s built-in system prompt: it is empty by default, and any value you set is appended to the built-in prompt to give the LLM extra context about your cubes. Reading it queries the server; assigning it takes effect on the next chat run and requires the ROLE_ADMIN role.

session.chat.system_prompt = (
    "The Quantity measure is expressed in units, not currency."
)

The system prompt is global: it applies to every request rather than to a specific cube (the assistant infers which cube a request targets). Use it for overall guidance.To give the assistant more information about a specific cube, set descriptions on its measures and hierarchies — for example cube.measures["Revenue.SUM"].description and cube.hierarchies["Product"].description. The assistant reads these descriptions through its tools. The Java SDK additionally accepts cube, dimension, level, and measure-folder descriptions through application.yaml.

How to serve no chat

Set AiConfig.chat_enabled to False to register no chat endpoint, as described in How to disable the chat endpoint.

How to opt out of dynamic tool discovery

Dynamic tool discovery is on by default. Turn it off with AiConfig.dynamic_tool_discovery, as described in How to opt out.

How Visualize This works
Set up Visualize This in Java
Set up Visualize This in Python
How to use Visualize This in the Atoti UI

Introduction to Atoti Intelligence

Releases and Upgrades

User Guide

Developer Guide

Configure Visualize This

Atoti Intelligence Essentials

Prerequisites

Atoti Java SDK

Configuration parameters

Alternative: XMLA_DESCRIPTION property

Partial configuration

How to disable the chat endpoint

Dynamic tool discovery

How to opt out

Atoti Python SDK

How to serve no chat

How to opt out of dynamic tool discovery

​Atoti Intelligence Essentials

​Prerequisites

​Atoti Java SDK

​Configuration parameters

​Alternative: XMLA_DESCRIPTION property

​Partial configuration

​How to disable the chat endpoint

​Dynamic tool discovery

​How to opt out

​Atoti Python SDK

​How to serve no chat

​How to opt out of dynamic tool discovery

​Related reading

Atoti Intelligence Essentials

Prerequisites

Atoti Java SDK

Configuration parameters

Alternative: XMLA_DESCRIPTION property

Partial configuration

How to disable the chat endpoint

Dynamic tool discovery

How to opt out

Atoti Python SDK

How to serve no chat

How to opt out of dynamic tool discovery

Related reading