Partial posting lets you post the valid data in a PLM staging journal and move only the failing data to a new staging journal for correction. A single validation error no longer stops the whole journal, so valid engineering data reaches D365 F&SCM without delay. Instead of fixing one error, re-running a full posting, and finding the next error, you correct only the transferred data.
With standard posting, one validation error prevents the entire journal from posting. On journals with tens of thousands of lines, a single bad line can block everything, and running a full posting again can take a long time. When you turn on the Transfer failed lines option, the system posts the valid data, moves the data that fails validation to a new staging journal (an error journal), records the reason for each transferred line, links the new journal to its source, and shows a summary. This works like the standard D365 F&SCM Transfer errors option used when you post financial journals.
The feature is available for manual posting (the Post journal dialog) and for the Post staging journals, Post migration staging journals, and Post release staging journals batch menus. It is not available for Import ECO.
Note
This feature is for users who post PLM staging journals to Microsoft Dynamics 365 Finance & Supply Chain Management, such as PLM Integration Administrators, Engineering Change Managers, and Master Data Managers.
The Transfer failed lines option
The option is available in the manual posting dialog and in the supported batch posting dialogs. It is set to No by default, applies to the current posting run only, and is not saved as a user preference.
Setting | Posting behavior |
|---|---|
No (default) | The system uses standard posting. If any validation error occurs, the whole posting stops, no lines post, and no error journal is created. |
Yes | The system posts the valid units and moves the units that fail validation to a new open staging journal. |
Turning on the option changes how validation errors are handled. It does not skip validation or post invalid data.
Note
The Validate journal action does not display the option. Posting runs validation again and then applies the selected posting behavior.
Prerequisites
Before you use partial posting, make sure that:
PLM integration is configured and active.
The PLM staging journal has status Open and contains lines to post.
You have permission to view, validate, edit, and post PLM staging journals.
The journal uses Import parts, Import migration, or Import release when you want to transfer failed lines.
The PLM staging-journal number sequence is configured so the system can create the new journal.
How partial posting works
When you post with Transfer failed lines set to Yes, the system:
Processes each atomic unit on its own.
Posts the units that pass validation to D365 F&SCM.
Marks the units that fail validation for transfer and records the reason.
If no unit failed, posts the whole journal and sets its status to Posted.
If some units failed, creates an error journal with the status Open and sets the source journal to Posted with errors transferred.
Shows a summary message.
When the option is No, the system validates all lines. If any line fails, it stops the whole posting and does not create an error journal.
Posting outcomes
Condition | What the system does | Source journal | Error journal |
|---|---|---|---|
All lines pass validation | Posts every line | Posted | Not created |
Some units fail, option is Yes | Posts the valid units and moves the failed units to a new journal, then shows a summary | Posted with errors transferred | Created, set to Open |
All units fail, option is Yes | Posts nothing and moves all units to a new journal | Posted with errors transferred | Created, set to Open |
An error occurs, option is No | Stops the whole posting; no lines post | Remains Open | Not created |
A journal-level error occurs | Stops the whole run, even when the option is Yes | Remains Open | Not created |
Note
Transfer applies to validation errors only. A system error, such as an infrastructure or database failure, stops the whole posting no matter how the option is set. A journal-level error, such as a missing target company on an Import release journal, also stops the complete run because it cannot be assigned to a single product group.
Posting units
The system posts a product and its related records together as one atomic unit. Related records include BOM lines, routes, route versions, attributes, documents, translations, and release targets. If any record in a unit fails, the whole unit transfers, so a product definition is never posted in part. Independent valid products still post, and different versions of the same item are separate units.
Supported scenarios
Scenario | Partial posting | Behavior |
|---|---|---|
Import parts | Supported | Posts valid products and transfers failed product groups. |
Import migration | Supported | Uses the same approach as Import parts. |
Import release | Supported | Posts valid product releases and transfers failed releases. The per-line target company is kept on transfer. |
Import ECO | Not supported | Uses standard posting. Import ECO creates an engineering change order, which is handled as a single unit, so the Transfer failed lines option does not appear. |
Validation information
Validation results appear on the journal lines. Journal line status shows OK or Fail, and Journal line message gives the reason for a failure. Related tabs, such as BOM lines and Route, also show the validation status for the selected product.
Error journals
An error journal is a new PLM staging journal that holds only the failed units, with the status Open. It keeps the original line data and order, adds a Transfer error reason on each line, and links back to the source through the Original journal No. field. You correct and repost it like any other staging journal. Some transferred lines may not show the original error, because they belong to the same unit as a failed record or depend on it.
The new journal uses the PLM staging-journal number sequence. To identify transferred journals easily, you can configure a distinct number sequence with a recognizable prefix, such as ERR-, for error journals in PLM parameters.
Journal statuses and results
After a partial post, the source journal becomes Posted with errors transferred and can no longer be edited, and the error journal is Open. If a corrected error journal still has failures, the remaining lines move to a further error journal, which creates a traceable chain.
A summary appears in the Infolog for manual posting, or in the batch history for batch posting. It shows how many lines posted, how many transferred, and the new journal number (line counts are journal lines, not units). The Related error journals FactBox links each source and error journal so you can follow the full chain, and you can filter the journal list by Posted with errors transferred or by Original journal No. to find journals that need follow-up. To keep large error sets manageable, set an Error journal lines limit in PLM parameters to split them into several journals.