Configuration package corrections
Processes incoming correction files, updates the configuration package in Dynamics, and reports the result.
Overview
Correction files for a configuration package must be applied in Dynamics. This automation reads the file, filters the package by cost code, year, and cluster, exports the data, creates the adjusted version, and imports it back. An email reports the outcome.
What has changed
- Less manual handling of corrections
- Corrections are processed faster
- Every run ends with a clear outcome
At a glance
In één oogopslag
Overzicht
Correction files for a configuration package must be applied in Dynamics. This automation reads the file, filters the package by cost code, year, and cluster, exports the data, creates the adjusted version, and imports it back. An email reports the outcome.
Wat er verandert
- Less manual handling of corrections
- Corrections are processed faster
- Every run ends with a clear outcome
How it works.
What it does per input file
- Picks up the next input file and converts it
- Extracts cost codes, batch year, and cluster number
- Opens the configuration package in Business Central and applies the filters
- Exports the current data and creates an adjusted version
- Imports the adjusted file and applies the package
- Emails the result and moves the input file to processed
Rules
The cluster number read back from the screen must match the file, with up to three attempts, and the adjusted file is retried up to five times. The automation only proceeds if the values are correct. The same input always leads to the same outcome, and every run leaves a log that can be audited.
Check out other automations.
Frequently asked questions.
No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.
Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.
Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.
Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.
Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.