Skip to main content

​
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:

​
Configuration parameters

The following table describes each configuration parameter:
Parameter nameDescription
system-prompt-pathsOrdered list of paths to system prompt files. Files are concatenated in the declared order and appended to the LLM context.
nameName of the cube to configure Visualize This for.
descriptionDescription of the cube.
dimensionsList of dimensions to provide additional information to the LLM.
  nameName of the dimension.
  descriptionDescription of the dimension.
  hierarchiesList of hierarchies to provide additional information to the LLM.
    nameName of the hierarchy.
    descriptionDescription of the hierarchy.
    levelsList of levels to provide additional information to the LLM.
      nameName of the level.
      descriptionDescription of the level.
measuresList of measures to provide additional information to the LLM.
  nameName of the measure.
  descriptionDescription of the measure.
measure-foldersList of measure folders to provide additional information to the LLM.
  nameName of the measure folder.
  descriptionDescription 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.

​
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. 
# Add extra context on top of the built-in system prompt
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.