Try your Business Central change in a sandbox first.
For the person who knows how the company works, and the partner or IT team who looks after Business Central. Describe a change in plain language. App Builder writes a real Business Central extension, builds it against your environment and publishes it to the sandbox environment you choose, for you to try. A finished change becomes a pull request your team reviews and merges.
In App Builder
You say the change in plain words
Say the rule your company works by, in a sentence, and choose how to work: together, with a plan first, or on its own. It asks when it is unsure, and you decide when it is done.
It works in your repository while you watch
It clones the app's repository into a workspace, reads how the app already does things and keeps a checklist you can follow. You correct it in the same plain words from the message box. The app's settings sit beside the conversation, with Build, Sandbox and Finalize one tab away.
App Builder in the UNI4C portal: a new change in CRONUS Extensions. The request: “Nobody should be able to release a purchase order whose posting date is outside the allowed posting dates.” Mode: Together, on the branch main.
Describe a change in plain language. App Builder writes a real Business Central extension, builds it against your environment and publishes it to the sandbox environment you choose, for you to try. A finished change becomes a pull request your team reviews and merges.
≈ €670.24 per person a month, excl. VAT. ≈ €7,372.65 a year if you pay yearly.
What you can build
- Fields, validations and defaults on the pages your team already uses
- Approval rules that match how your company actually decides
- Lists and views shaped around a job, not around a table
- Prototypes worth throwing away, to find out whether the idea holds
Your repository, your reviewer, your production environment
- Repository
GitHub, Azure DevOps, GitLab, or hosted by UNI4C
Every session works in one repository, so the prototype and the finished extension are the same project.
- Review
It ends as a pull request
A finished change opens a pull request in your repository. Your team reads it and merges it, or discards the change.
- Production
Nothing reaches it on its own
It builds against your environment's symbols and publishes to the sandbox environment you choose. Moving the change to production is your team's step, not the session's.
For whoever looks after Business Central
- Developer sign-in
One per tenant, shared by every app that targets it
It is kept in App Builder, apart from the connections in your account, so adding it once covers every app you build for that tenant.
- Code review
Every AL change checked against BCQuality
Microsoft's open knowledge base of Business Central quality rules, with UNI4C's own on top. What it finds is written into the pull request, so your reviewer starts from it.
Why you can use this without being a developer
- It asks, it does not assume
The questions come to you in your own language
Where a rule could go two ways, the session stops and puts the choice in front of you as a sentence with two answers. You are being asked a business question, which is the only kind you should have to answer.
- Wrong is cheap
A monthly cap, and the spend on each change
Sessions spend against a monthly budget in euros, set by your administrator or UNI4C, and each change shows what it has spent. Trying again takes one correction, which is what makes it worth testing an idea before anyone writes a specification for it.
- It does not stop at easy
The same project a developer works in
Plain language is the way in, not the ceiling. Underneath it is a full Business Central development suite in your own repository, so the prototype you started is the thing a developer can finish. Nothing is rebuilt to make it real.
Bring the change you have been asking for since last year
The useful test is the small app your team has wanted for months and nobody has had time to build. Start a trial, or book a demo and bring it with you.
Or write to us at hello@uni4c.ai