Skip to content
HomeDemosDocsChangelogPricing
Log In
Get MapSVG
MapSVG 9/Documentation/AI assistant

AI assistant

The AI panel can explain MapSVG and perform supported editing tasks when its module, license, and connection are configured. Open it with AI in the editor toolbar.

Give a specific task

Section titled “Give a specific task”

Name the App component, the intended data source, and the result you want. Examples:

  • “In this App, make region fills #1274b7 and borders white. Keep the map background white.”
  • “Add a category select filter for the Objects binding. Use the category field’s existing values.”
  • “Explain how this Page’s Objects Query is connected. Do not change anything.”

Distinguish discussion from execution. If you only want advice, say so. Region colors, App background, filter form fields, and Collection fields are different editing scopes.

Review changes

Section titled “Review changes”

The assistant operates through available tools and the current editing context. Read its reported actions and inspect the actual preview/settings. Do not treat a confident text answer as proof that a change reached the correct draft or rendered successfully.

Check Versions and the draft status after a mutation. Use normal Publish when the draft is ready. If asking AI to Publish, expect the same explicit publication confirmation rather than assuming that autosave made the change live.

Data and prerequisites

Section titled “Data and prerequisites”

Tell the assistant whether records are Regions or Objects. Regions use SVG geometry and cannot have Location fields; Objects can provide markers through Location.

Google-dependent work requires a configured key. Do not paste private credentials into chat. Set credentials through the installation’s designated settings.

Shared Database edits affect every consumer of that resource, even when requested from one App’s chat. Specify whether you want to change the App binding or the shared Query/Collection.

If an attempt fails

Section titled “If an attempt fails”

Read the tool error, verify the selected App and source, and make the next request narrower. Repeating the same request cannot repair a missing field or invalid Query ID by itself.

Avoid the current Details View action in required workflows. Use the documented Popover path until its instance-selection issue is resolved.