Documentation
What BC Toolkit does, how it connects to your Business Central tenant, and what to expect from a bulk-correction job.
Requirements
- Microsoft Dynamics 365 Business Central online (Essentials or Premium). On-premises deployments are not supported.
- A Microsoft Entra ID Global Administrator to grant consent once per organisation.
- Users need an existing Business Central user account and licence. BC Toolkit never bypasses Business Central permissions.
Connecting your organisation
- Your Global Administrator opens the consent link we send you and accepts the permissions requested by BC Toolkit, published by CLOUD DATA PROCESSING LLC.
- Users in your organisation sign in at BC Toolkit with their Microsoft work account and choose an environment and company.
- Consent can be revoked at any time by your administrator in Microsoft Entra ID under Enterprise applications. Revoking it ends all access immediately.
Permissions requested
| Permission | Why |
|---|---|
| Dynamics 365 Business Central: Financials.ReadWrite.All (delegated) | Read metadata and records, and write the corrections you approve, as the signed-in user. |
| Microsoft Graph: openid, profile, email, offline_access (delegated) | Sign the user in and keep the session alive without repeated prompts. |
No application-level (unattended) permissions are used in the hosted service.
Exploring
After sign-in, BC Toolkit reads the environment's API metadata and lists every entity it exposes: standard pages, extension pages and custom API pages. Each entity can be browsed with filters, sorting and field selection. Relationships are navigable, and enumeration values and bound actions are shown next to the fields that use them.
Bulk corrections
- Describe. Choose the entity, the records (by filter or by key), the fields and the new values. Values can be constants or derived from other fields of the same record.
- Plan. BC Toolkit fetches the current records and produces a diff: for every record, every field that would change, old value and new value. Records that would not change are left out.
- Apply. Only after you approve the plan are the updates sent, in batches, with each record's version tag, so a record changed by someone else in the meantime is rejected by Business Central and reported, never overwritten.
- Report. Each run produces a report listing every record written, every record skipped and every error message returned by Business Central.
- Undo. A run report can be turned into a reversing job, which goes through the same plan and approve steps.
Read-only environments
An environment can be marked read-only in BC Toolkit. Browsing works; planning works; apply is refused. Use it for production environments you want to inspect but not change from here.
Data handling
Business Central data is read on demand and shown to the signed-in user. BC Toolkit stores job definitions, plans and run reports so that runs can be reviewed and undone. It does not keep a copy of your Business Central database. See the privacy policy for details.