DatAInsights Composer Editing and History

Premium

Updated on Nov 4, 2026

Users can refine generated visualizations with follow-up prompts and return to previous versions through History. Your application can also persist results between visits.

View and Edit Modes

A generated visualization is displayed in one of two modes:

• View mode—The component displays the Grid, Chart, or Gauge together with a Refine and Remove button.
• Edit mode—The component displays a prompt for refining the result with Confirm, Discard, and History buttons.

A visualization that the AI generates opens in edit mode, so the user can approve it. A visualization that the app supplies through the configs or defaultConfigs property opens in view mode instead.

History

Each successful generation or refinement adds a version to History. Select an earlier version to restore it. Refining a restored version replaces any newer versions.

Persisting and Restoring Visualizations

Handle onConfirm to store the current configurations, and pass them to defaultConfigs to restore the visualization. To persist History as well, store the history from onHistoryItemCreate and restore it through initialHistory.

The following example saves visualizations and History in browser localStorage. Generate a visualization, select Confirm, and run the example again to restore it.

Example

View Source

Loading ...

You are responsible for securing persisted configurations and History, including data in localStorage. Follow the application security responsibilities.

Suggested Links

• DatAInsights Composer Controlled Mode
• DatAInsights Composer Events
• DatAInsights Composer Accessibility
• API Reference of the DatAInsights Composer