Good Examples
Specific prompts that name the fields, filters, grain, and sort order get the best first result:
- “List all closed claims in 2021 with claim number, closed date, loss state, and paid amount.”
- “Starting from Policy Renewals stock report, add agency name and filter to Texas policies only.”
- “Group claims by peril and month, return claim count and total paid, sorted by month.”
Follow-Up Prompt Examples
Once the first result is on screen, keep refining in the same conversation:
- “Remove claim_id and add full property address.”
- “Change grain to one row per policy per month.”
- “Keep all logic but only include rows where written premium > 0.”
Example Scenarios
Scenario A: Fixed-Format Text Output
Request explicit file structure, including column order, delimiters, or widths, then confirm formatting requirements in follow-up prompts. Run and inspect output carefully, since formatting defects are often discovered downstream by consuming systems.
Scenario B: Specs or Documentation Context
Paste relevant specification details into the Copilot conversation, ask it to conform the SQL to the schema contract, and validate that generated fields and transformations match requested definitions exactly.
Scenario C: Parameters and Formats
You can ask the Copilot to make a report reusable rather than hard-coding values. For example, “Make the start and end dates parameters with the end date defaulting to the last day of the previous month, and format Total Paid as currency.” The Copilot adds the '<<$StartDate>>' and '<<$EndDate>>' placeholders and sets up the parameter defaults; confirm them in the Parameters panel and the column formats in the results grid before you save.
Scenario D: BriteData Report Migration
When you open a legacy BriteData report in SQL Editor, the Copilot offers to translate it to SQL. The migration is driven by the report's definition rather than a prompt, but you can still guide it in chat, for example, “Keep the claim number as the first column and add a summary sheet grouped by adjuster.” See Migrating BriteData Reports with Report Copilot.
