Skip to main content

Overview

Changing a parameter in Dynamics 365 Finance & Operations means editing production configuration in place. There is no draft to review, no history to audit, and no clean undo. A single wrong value can ripple across the business, and because the only safe moment to change anything is when nobody is using the system, configuration change becomes a tense, after-hours event.

Ballast exists to make that not true. It brings date-effective versioning and governance to parameter tables, so a configuration change stops being a live edit and becomes a managed change.

What working with Ballast looks like​

Instead of typing a new value into a live parameter form, you stage the change as a draft snapshot. The draft is a real, reviewable object: you can compare it side by side against what is currently live and see exactly which values differ before anything takes effect.

When the draft is right, you schedule it. The change takes effect at exactly the date and time you choose, which means a cutover no longer requires someone at a keyboard at midnight. The system applies the change at the scheduled moment, on time, every time.

And if something is off, you roll back cleanly. Because every version is kept, reverting is a governed operation with its own audit trail, not a scramble to remember what the old values were.

Every change, in either direction, lands in a full configuration history: what changed, when it took effect, and who staged it. When controls or compliance ask how a parameter came to hold its current value, the answer is a query, not an investigation.

Who it is for​

Ballast is for any team that has been burned by a live configuration edit, and for any team whose auditors ask questions the standard platform cannot answer. It installs into your own environment as a package and is maintained across Finance & Operations releases, so the governance you put in place stays dependable as the platform evolves.

To stage your first draft in a sandbox, free and without a time limit, see Get started. The versioning model itself is described in Concepts.

What's included​

  • Date-effective parameter versioning
  • Draft snapshots and staging
  • Scheduled effective dates
  • Compare a draft against what is live
  • Clean, auditable rollback
  • Full configuration change history