Use the assistant
The assistant is a prompt or chat attached to a grid. Use it to describe the view or operation you want. The available operations depend on how the application was configured.
If you are exploring for the first time, open the AI Grid Assistant demo. Start with its suggested requests: the default demo recognizes predefined prompts without calling a model.
Make your first request
Section titled “Make your first request”- Choose a suggestion, or type a request if your application has a connected model. Start with one specific task, such as “Show only Europe”.
- Press Enter to submit. Use Shift+Enter for a new line.
- Wait for the response and inspect the grid. A filter or sort can apply immediately; a supported data edit opens a preview.
- If the assistant asks a question, choose one of its suggested answers or submit a more specific request.
Use the column names and values you see in the grid. Start with a single operation and check the result before continuing.
Requests to try
Section titled “Requests to try”These examples assume an orders grid with Amount and Region columns. Your application’s names and permissions may differ. In the scripted demo, use the displayed suggestions for supported examples.
| Your goal | Example request | What to expect |
|---|---|---|
| Narrow the view | “Show orders above 1000” | A filter on Amount. |
| Reorder the view | “Sort by amount descending” | The largest amounts appear first. |
| Ask about available columns | “Which columns can I sort?” | An answer based on disclosed metadata, with a connected interpreter. |
| Ask for a total | “What is the total amount?” | Requires enabled analytical reads; a written summary also needs result-to-answer configuration. |
| Change a record | “Set order 1042 amount to 1200” | Requires enabled editing and a stable record ID; review the preview before applying. |
An unavailable action cannot be enabled by asking for it. Your application developer must configure the capability and permissions.
Review an edit before applying
Section titled “Review an edit before applying”When a proposed data or column change appears, read its summary and details. Check the target records, fields and new values.
- Select Apply to commit the prepared change.
- Select Cancel to discard it without changing the data.
- If the data changed while you were reviewing, submit a fresh request so the preview reflects the current state.
Filtering and sorting change the view immediately. Custom application actions can have their own approval and undo behavior.
Understand the history controls
Section titled “Understand the history controls”The assistant keeps view changes, data edits and chat messages separately. Controls appear when relevant to your configuration and current state.
| Control | What it does |
|---|---|
| Stop | Cancels a pending request. It does not undo an operation that already completed. |
| View steps | Show filter/sort requests. Remove an individual step to update the view without that request. |
| Restore previous view | Returns to the view before the latest assistant filter/sort step. It can refuse if the view has since changed manually. |
| Reset view / view-trail Clear all | Restores the assistant’s starting filter/sort view and clears its view steps. |
| Undo / Redo | Uses configured data/action history for supported edits. |
| Clear chat | Clears displayed messages and enabled model conversation memory. It preserves the grid and view steps. |
Clearing chat history does not undo edits. Use the appropriate view or data history control for the change you want to reverse.
When a request does not work
Section titled “When a request does not work”| What you see | What to do |
|---|---|
| A clarification question | Choose an offered answer, or name the column, value or record more precisely. |
| Unsupported request | Try an available suggestion. Ask your application developer whether the operation is enabled. |
| No rows after filtering | Check the value and filter criteria; use Restore to return to the previous assistant view. |
| Stale result or preview | The grid changed during the request. Check its current state and submit again. |
| Connection or authentication error | The application developer should check the interpretation endpoint and session. |
| A request limit message | Wait for the application’s indicated retry time. Repeated requests can consume more quota. |
Totals from the local grid cover its expanded visible rows. A loaded page is not the full remote dataset. For complete server totals, the application needs an appropriate server-side action.
Next: Connect your first assistant if you are integrating it into an application, or return to the overview to choose a guide.