Use this section as a triage map. Start with the symptom you observe, then apply focused checks before rewriting the full query.
No Rows Returned
- Confirm date ranges and filters.
- Validate parameter values and types.
- Run a simplified version first.
Duplicates or Inflated Totals
- Check join keys and grain.
- Aggregate at the correct level before joining when needed.
Unexpected Nulls
- Validate join direction and optional dimensions.
- Use explicit null handling, such as COALESCE, where appropriate.
Report Save Failure
- A hidden parameter has no default value. Give it a default or make it visible.
- The SQL uses a materialized view whose measures require a parameter (AsOfDate, or StartDate and EndDate) that is not declared. Add the parameter named in the error message.
- A "Value of another parameter" default refers to a parameter that does not exist. Pick a parameter from the list.
Wrong Parameter Value at Run Time
- Confirm the placeholder in the SQL is wrapped in single quotes:
'<<$EndDate>>'. - Do not include quotes in a static default value; the SQL supplies them.
- For a scheduled run that produced unexpected results, check the schedule's parameter overrides. If a schedule needs a dependent parameter such as AsOfDate, add an override for it with the same SQL expression used for EndDate.
Incorrect Excel Formatting
- Open the report, run it, and check the format selector above the column. Set it explicitly and save.
- Percentages 100 times too large or too small: the SQL multiplies by 100 and the column is also formatted as Percent. Use one or the other.
- ZIP codes or phone numbers losing leading zeros: set the format to ZIP/Postal or Phone.
- Formats are only applied to Excel output. CSV, TXT, and JSON output contain raw values.
- If the format selectors are not shown, the last run did not complete. Fix the query and run again.
BriteData Migration Problems
- "No past execution found": run the BriteData report once from the Report List, or attach a previous output file to the Copilot chat.
- "Not supported for migration": the report was not included in the migration survey. Contact support to add it.
- Migrated report is missing a summary sheet or shows different totals: see Migrating BriteData Reports for what to check.
Unexpected Copilot Output
- Clarify grain in plain language, for example, “one row per claim.”
- Provide exact fields and sort order.
- Ask Copilot to explain its assumptions before generating final SQL.
