When an import error occurs, the Import Export PowerTool fails the entire table being imported and rolls back everything it wrote for that table, rather than skipping a single bad line and continuing. This is a completely free app from Insight Works for Business Central. The tool reports the line that caused the failure so you can correct your file, but there is no per line staging step that lets you review and accept partial results.
How a failure is handled
The tool writes directly to Microsoft Dynamics 365 Business Central tables as it imports. If it reaches a row that cannot be processed, for example a record that already exists when only inserts are allowed, it stops and reports the specific line and the reason. At that point everything imported for that table is rolled back as if it had never been loaded. If a file has one hundred lines and the failure occurs on line ninety nine, the previous ninety eight lines are also rolled back. You then fix the data and run the import again.
No intermediate review stage
This is an important difference from RapidStart configuration packages, which stage imported data so you can review failed lines and correct them before committing. The Import Export PowerTool does not provide that intermediate review step. Because it writes straight to the tables, the result is all or nothing for each table. The benefit of this design is speed and simplicity. The trade off is that you should validate your file before importing rather than relying on the tool to hold back questionable rows.
Commit behavior across multiple tables
A single file can contain many tables. The commit behavior option determines what happens at table boundaries. When commit after each table is in effect and your file contains, for example, six tables, the first five are committed as they complete. If the sixth table fails, the five already completed remain imported, and you only need to restart from the sixth table. This limits the rework when a large multi table load encounters a problem partway through, while still treating each individual table as all or nothing.
Reducing the chance of failures
Because the import is all or nothing per table, a little preparation pays off. Confirm whether each record should be inserted, updated, or both, and set the insert and update options to match. Use the option that prompts on missing fields or tables so you can catch a mismatched column before it stops the run, or choose to ignore missing fields when you intentionally include columns that do not exist in the target. Validating only the fields that need the underlying business logic, rather than every field, also reduces unexpected errors and speeds the load.
Related Tools
Import Export PowerTool is the Insight Works app for fast import, export, update, and delete operations in Business Central. Its error handling rolls back by table and its commit behavior option controls how multi table files are committed.
In short, the tool fails and rolls back by table, not by line, and it does not offer a staging area for partial acceptance. Prepare and validate your files in advance, use the missing field prompts, and rely on commit after each table so that a problem late in a large load does not force you to repeat the work that already succeeded.