Multi-Level Production BOM Editor — help

1. What the app does

The Multi-Level Production BOM Editor shows a production BOM and all of its nested child BOMs as one tree inside Business Central. You can review the whole structure, then start an explicit editing session in which changes are staged rather than written straight through.

Opening the tree and staging changes never puts your source BOMs Under Development. Source production BOMs keep their existing status until you choose Save and Certify.

2. Requirements and permissions

• Microsoft Dynamics 365 Business Central online with a Premium licence and Manufacturing enabled.
• The BSL BOM Editor View permission set for read-only access to the tree.
• The BSL BOM Editor Edit permission set to start an editing session and save.
• SUPER is not required. Assign the app permission sets alongside your normal manufacturing permissions.
• The app is standalone: it does not depend on other Boeksolutions or third-party extensions.
• The product interface is available in English and Dutch.

3. Opening the editor

• From the Item Card: open the item and choose the Multi-Level Production BOM Editor action. The tree opens on the production BOM linked to that item.
• From a Production BOM: open the production BOM (or version) and choose the same action. The tree opens on that BOM as the root.

The tree always opens read-only.

4. Reading the tree

Each row is a component line in a production BOM group. Indentation shows the parent-child relationship: an indented block belongs to the line directly above it that acts as a sub-assembly.

• Line Type, No. and Description identify the component.
• Quantity per shows the quantity with its full precision, so rounding is visible.
• Unit of Measure Code and Routing Link Code are shown as stored on the line.
• The shared indicator marks a BOM used by more than one parent. Changing it affects every parent that uses it.
• Change type shows whether a line is unchanged, added, modified or deleted in the current session.
• Validation message shows the standard Business Central message for a line that cannot be applied as staged.

5. Expanding and collapsing

Expand and collapse behave like any standard Business Central tree control. Use the expand indicator on a row, or the keyboard right and left arrows, to open and close a sub-assembly. Collapsing a group does not discard staged changes inside it.

6. Searching and filtering

Search uses standard Business Central filter syntax, so the expressions you already use elsewhere work here:

7. Start editing

Choose Start Editing to open a staged editing session. From that moment the tree accepts changes, and every change is marked with its change type. Nothing is written to the source BOMs yet.

8. Editing component fields

Within an editing session you can change the following fields on a component line, using the standard Business Central lookups:

• Line Type
• No.
• Quantity per
• Unit of Measure Code
• Routing Link Code

9. Adding a line

A new line is always placed under the exact BOM group you selected. Select the group you want the component to belong to before you add, and check the indentation afterwards to confirm the placement.

10. Deleting and moving lines

Deleting and moving are limited to siblings within the same BOM group. You can reorder a line among its siblings, but you cannot move a line from one BOM group into another. To relocate a component across groups, delete it in one group and add it in the other.

11. Save and Certify

Save and Certify applies the whole staged change set in one step. The sequence is:

• Concurrency is rechecked against the current data, so changes made by someone else since you opened the tree are detected.
• Standard Business Central validation runs on every affected line.
• All changes are applied inside a single transaction.
• Child BOMs that were originally certified are restored to certified before their parents, so the structure is certified bottom-up.
• If any step fails, the entire transaction is rolled back and nothing is applied.

After a rollback your staged changes remain in the session, together with the validation messages, so you can correct and retry.

12. Cancel Editing and interruptions

Cancel Editing discards the staged change set and returns the tree to read-only. Because nothing was written, the source BOMs are unaffected.

If the browser tab closes or the connection drops before save, no staged change is applied to the source BOMs. Reopen the same item or BOM to resume the current staged session when it still exists. If it was cancelled or the app says the session is incompatible, start a new session.

13. Shared BOMs and concurrent changes

A shared BOM is used by more than one parent. Editing it changes the structure everywhere it is used, not only in the branch you are looking at. Check the shared indicator before changing a sub-assembly.

If another user changes an affected BOM while your session is open, the concurrency recheck at save time stops the save. Reopen the tree to load the current data before staging your change again.

14. Troubleshooting

15. Contacting support

Email info@boeksolutions.nl and include:

• The environment type (sandbox or production) and the app version.
• The Business Central country/region version and the company name.
• The exact action you took and the exact message text.
• The item, production BOM or version number involved.
• The approximate date and time, including time zone.

Do not send passwords, access tokens, licence keys or other secrets, and do not send confidential data that is not needed to reproduce the issue. Redact anything that is not relevant.