What the product does.
WexaSQL is a native Dynamics 365 Finance query and data-exploration product. The query editor is SELECT-only. Data investigation and record changes have distinct workflows and permissions.
The native development model has build evidence. A clean customer installation, distributable package, licence delivery and authenticated runtime acceptance are still required before a customer deployment is treated as accepted.
Product capabilities
Query and data exploration
Prepare SELECT queries and inspect the result within the agreed Finance access and company context.
- SELECT query workspace
- Metadata and result review for the evaluated package
- Arbitrary UPDATE and DELETE are outside the query editor scope
Development candidate capabilities
The following features are implemented in the local candidate and must be confirmed in the installed package during the demo.
- INNER, LEFT, RIGHT, FULL OUTER and CROSS JOIN across tables
- CSV result export
- Authenticated runtime acceptance of candidate behaviour is pending
Controlled record editing
A separate prepare-and-commit workflow controls any permitted record changes.
- Allowed-field scope
- User, session and company checks
- Audit and conflict handling
- Roles and change responsibility confirmed during implementation
Licence and delivery
The documented licence model separates Free and Pro capabilities for registered tenants.
- Product-specific tenant grant
- No automatic key or trial activation
- Application/platform versions and dependencies agreed per package
- Customer installation, runtime acceptance and support scope confirmed before delivery
Evaluate the relevant tasks.
Use these tasks to prepare a demo. Confirm the supported behaviour for your version and operating environment.
- Describe one data question and provide anonymised table and field names; keep business records, credentials and connection strings out of the enquiry.
- Confirm the Finance application/platform version, proposed model/package and the roles used for evaluation.
- Review a SELECT result and any required INNER JOIN or other multi-table query in the installed candidate; record the result and access context.
- Check CSV output only if included in the evaluated package, using non-sensitive sample rows.
- Review a record-change scenario separately, including permitted fields, preparation, commit, conflict handling and audit evidence.
- Agree the Free / Pro grant, customer installation test, runtime acceptance and support responsibilities before delivery.
Workflow walkthroughs
Review a SELECT query
Check the query behaviour your investigation needs in the agreed environment.
- Confirm the evaluated package and account permissions
- Prepare a SELECT query with anonymised sample context
- Inspect columns, returned rows and company context
- Record any unsupported field or join behaviour before agreeing delivery
Evaluate the JOIN candidate
Confirm multi-table query flexibility without treating local implementation as customer acceptance.
- Choose a representative INNER JOIN or another required join type
- Confirm that the installed package contains the candidate implementation
- Review query validation and returned columns
- Record runtime evidence and any unresolved cases
Review a permitted record change
Evaluate the separate controlled workflow using a disposable sample record.
- Agree the allowed field, role and environment
- Review the prepared change and current record context
- Confirm the explicit commit and conflict behaviour within the agreed demo scope
- Inspect audit evidence and acceptance criteria
Prepare a useful support request.
Include the evaluated WexaSQL package, Finance versions and the query or controlled-change scenario that needs review.
- Share anonymised table/field names and the exact error message.
- Include role, company context and package version when known.
- Leave out query results containing personal, financial or customer records, and never include credentials.
- Distinguish a local candidate issue from the behaviour of an accepted customer package.
Your questions, answered.
Can the query editor write arbitrary SQL?
No. The editor is SELECT-only. Permitted record changes follow a separate controlled prepare-and-commit workflow.
Are JOIN and CSV export accepted customer features?
They are implemented in a local development candidate. Their presence and behaviour must be validated in the installed package; customer runtime acceptance is not yet established.
What release version should we install?
A public semantic release version is not confirmed. The proposal identifies the exact package, dependencies and compatible Finance versions before installation.