Product & usage
When to use SWQL Copilot vs hand-writing SQL
Copilot for exploration and drafts; hand-written SWQL plus review for production gates.
Use Copilot first when
- You know the business object but not the exact entity / relationship names.
- You want multiple skeletons quickly to compare in the lab.
- You need a plain-language explanation of legacy SWQL.
Open SWQL Copilot and paste constraints from your ticket.
Prefer hand-written (and review) when
- Queries run under production read-only roles with strict performance limits.
- Change management requires frozen text and sign-off.
- You rely on version-specific views that must not drift.
Workflow
Draft → validate on a small row set → promote after review.