Business Central customisations, from request to .app
These are the customisations companies ask for most. For each one: what you would write in your request, and what the agents build in AL. Every extension is compiled for your Business Central version and approved by your people before it is released.
Reports and document layouts
Sales by salesperson and item
You ask: “A monthly report of sales by salesperson and item, with the margin, that I can filter by date and open in Excel.”
The agents build: A report with its dataset and an Excel layout, filters for dates and salespeople, and the permission set that lets your sales managers run it.
An invoice that looks like yours
You ask: “Our sales invoice with our logo, our bank details and a note for the customer, in Italian and in English.”
The agents build: A layout for the posted sales invoice with translated captions, and an install routine that makes it the default.
Fields, tables and pages
More information on the customer
You ask: “A customer category and a sales region on the customer, copied to every sales order and shown on the posted documents.”
The agents build: Table extensions on the customer and the sales documents, page extensions for the cards, and event subscribers that copy the values when a document is created and posted.
A register of supplier certifications
You ask: “A list of our suppliers' certifications with their expiry dates, and a warning when one is about to expire.”
The agents build: A new table with list and card pages, a FactBox on the vendor card, and a list of the certifications expiring in the next 30 days.
Validations and controls
No order without a reference
You ask: “Block the release of a sales order when the customer's reference is missing, for the customers who require one.”
The agents build: A field on the customer that marks who requires it, and an event subscriber on the release of sales documents that stops it with a clear message.
Prices below cost
You ask: “Warn the user when a sales line is priced below its cost, and let only some people confirm it.”
The agents build: An event subscriber on the sales line that compares price and cost, a setup field naming who may confirm, and the confirmation recorded on the line.
Integrations
Suppliers' price lists from a file
You ask: “Import our suppliers' price lists from a CSV file every week.”
The agents build: An import that maps the file's columns to purchase prices, with a log of the rows it could not import and why.
Tracking from the courier
You ask: “Show the courier's tracking status on the posted shipment.”
The agents build: A codeunit that calls the courier's REST API, a field and an action on the posted shipment, and the credentials kept in isolated storage, never in the code.
Automation
Statements for overdue customers
You ask: “Every Monday, email a statement to each customer with overdue invoices.”
The agents build: A codeunit run by the job queue that finds the customers with overdue invoices and emails them the statement, with a setup page for the day and the text.
A price increase in one step
You ask: “Raise the sales prices of one item category by a percentage, from a given date.”
The agents build: A batch job with filters for category, percentage and date that writes the new price lines and leaves the old ones as they are.
Translations and help
Your extension in your users' languages
You ask: “Our users work in Italian and German.”
The agents build: Translation files (XLIFF) for every caption, tooltip and message of the extension, produced together with it.
Help where it is needed
You ask: “Explain the new fields to the people who will use them.”
The agents build: Tooltips on every new field and action, written for your users and translated with the rest.
Is your customisation not on the list?
Describe it in your own words: the agents ask about whatever is unclear and propose a plan before anything is built.
Read the guide to AI and AL development for Business Central