Skip to content
Import Export PowerTool app iconImport Export PowerToolImport

Per-Table Commit for Microsoft Dynamics 365 Business Central

When one import file carries many tables, an error in the last table can roll back everything that loaded before it, and the whole file has to run again. Import Export PowerTool can commit an import per table, so tables that loaded successfully stay in place when a later table fails. This is a completely free app from Insight Works for Business Central.

How Per-table commit works in Import Export PowerTool

  1. Prepare a file with several tables.
  2. Set the Operation to Import and choose to commit per table.
  3. Run the import; each table is committed when it finishes.
  4. If a later table fails, fix it in the file and import that table again.

Key capabilities

Table by table

Each table is committed once it imports, rather than holding the whole file in one transaction.

Shorter reruns

After an error, correct the failing table and import it again instead of reimporting every table in the file.

Suits large files

Per-table commit matters most for bulk imports that load many related tables at once.

Works with the other options

Per-table commit sits alongside insert and update control, validation, and missing field handling, so the rest of the import behaves the same way.

Details that matter on the floor

Plan the table order

Related tables usually load in order, for example a header table before its lines, so a failure part way through leaves a predictable set of tables loaded.

Who uses Per-table commit

Data migration specialists

Run large multi-table files without restarting from the beginning after an error.

Business Central consultants

Recover quickly from a data problem found late in a go-live load.

Questions about Per-table commit

If one table in my import fails, do I lose the others?

Not when you commit per table. Tables that already imported stay committed, and you rerun only the table that failed.

Why not always commit per table?

Committing the whole file at once keeps an all-or-nothing load. Per-table commit trades that for shorter reruns after an error.

Is per-table commit meant for large migration files?

Yes. It suits files that carry many tables, so an error late in the file does not require a full reimport.

Import Export PowerTool app icon

Part of Import Export PowerTool

Import, export, update, and delete Business Central data in bulk, for data migration and ongoing data management.

Have a question about Per-table commit?

Send us a note and the Import Export PowerTool team will reply by email. Ready to plan a rollout? Contact your Microsoft Partner.

Ask a product question

Product Questions