Why You Can't Delete That Dimension Value

What BC Actually Checks

When you delete a dimension value, BC asks one question: has this value ever appeared in a dimension combination?

• Each unique combination of dimension values (for example, DEPARTMENT 20-200 + PROJECT A) is saved once and given an ID.
• Saved combinations are never removed, even when nothing uses them any more.
• So if the value was ever put on a combination, the delete is blocked for good. This includes posted entries, budget lines, and even an order or journal line that was later deleted.

The one case where the delete works: the value was set up but never used anywhere. Its only links are default dimensions on customers, vendors, items or accounts, and BC removes those for you when you delete the value.

Things That Won't Help

What About Dimension Correction?

Dimension Correction can't delete the old value, but it can fix your reporting, which is often what the client actually wants.

What it does:

• ✅ Moves historical G/L entries from the old value to the new one
• ✅ Updates analysis views, so financial reports and account schedules show the corrected structure
• ✅ Can be undone if you get it wrong

What it doesn't do:

• ❌ Change customer, vendor, item, fixed asset, job or bank ledger entries. Those keep the value they were posted with, which is correct.
• ❌ Make the old value deletable. It gives the corrected entries a new combination and keeps the old one, which is also what lets you undo the correction.

When to use it: The value was wrong, not just untidy, and you want G/L history reported under the right value. Run the correction, then block the old value as described below.

What to Do Instead: Block It, in This Order

1. Find work that's still open. Look for open sales and purchase documents, unposted journal batches, and recurring journals that use the value.
2. Re-code or finish that work. Otherwise it fails to post once the value is blocked, and someone finds out on Monday.
3. Remove the default dimensions that point to the value on customers, vendors, items, G/L accounts, resources and jobs.
4. Optional: Run Dimension Correction to move G/L history to the new value.
5. Set Blocked on the Dimension Values page.

What blocking does:

• ✅ Stops the value from being used on new transactions
• ✅ Keeps all history intact. Reports, Analysis by Dimensions and account schedules still show it.
• ❌ Doesn't remove it from the list. If clutter is the issue, use Indentation and Totaling to group old values.

The Real Lesson: Design Dimensions Before Go-Live

Treat the dimension value list as part of the audit trail, not as a settings list. Once a value is used, it's as permanent as your ledger, and that's on purpose.

If your structure turns out to be wrong:

• Do: add new values or a new dimension, use Dimension Correction to fix G/L reporting, block the old values, and keep them for historical reporting.
• Don't: try to remove what's been used. No supported way exists.

Decide how many dimensions you need, at what level of detail, and which ones are mandatory before go-live. After go-live, all you have left is Blocked, Dimension Correction for the G/L, and a naming convention.

This post came from a Dynamics Community forum thread asking how to trace Dimension Set ID 3 back to the record blocking a delete. Five people answered "block it." They were right. This post explains why.