Explorer View

The Explorer view in Max allows users to directly query data using SQL within the context of a specific connection. It is designed for technical users such as analysts or developers who are comfortable writing SQL.

Overview

The Explorer interface includes:

• A SQL editor at the top for writing your query
• An Execute SQL button to run the query
• A results pane at the bottom that displays returned rows from the query

Key Features

• Connection-Specific Access: Queries run using the authentication provided by the selected connection. This ensures that access respects all permissions and credentials tied to that data source.
• Direct SQL Access: Write custom SQL queries to explore, validate, or troubleshoot data directly.
• Real-Time Results: After executing a query, results are displayed immediately in the lower pane for review.

Common Use Cases

• Explore raw data before building an assistant skill
• Troubleshoot issues with metrics or filters
• Run ad-hoc analysis outside of a skill flow

Notes

• Make sure the connection you're using has the necessary permissions and that you are authorized to access it.
• The Explorer only shows data that is returned by the executed SQL
• Long-running queries may be subject to timeouts or result limits depending on your connection's settings.

Creating and Using Examples

Examples help improve SQL generation in the Data Explorer by providing the system with reference patterns for how to interpret and respond to similar questions.

Creating Examples from Data Explorer

When you find a question and answer pair that works well in Data Explorer:

1. Save as Example: Click the "Add to Examples" button
2. What gets saved:

• The natural language question you asked
• The SQL query that was generated
• The relationship between them

This example then becomes available to the Data Explorer skill in chat, helping it generate better SQL for similar questions in the future.

Managing Examples

Viewing Examples

1. Navigate to the Examples tab in Data Explorer
2. Review all currently configured examples for your dataset
3. See how questions map to SQL queries

Editing Examples

When adding an example after SQL has been generated:

1. Modify the question: You can change the natural language question before saving
2. Keep the SQL: The generated SQL remains the same
3. Save: This creates an example with your modified question paired with the original SQL

This is useful for:

• Creating variations of questions that should produce the same SQL
• Simplifying complex questions while maintaining the correct query
• Building a comprehensive example library for common query patterns

Best Practices

• Save successful queries: When Data Explorer generates correct SQL, save it as an example
• Create variations: Use the question editing feature to create multiple phrasings for the same query
• Regular review: Periodically review your examples to ensure they remain relevant
• Cover common cases: Build examples for frequently asked questions in your organization