Skip to Content

MC1536019 Dynamics 365 Supply Chain Management: Known issue affecting 10.0.49 PQU-1 and PQU-2

Summary

  • Microsoft identified a code regression in Dynamics 365 Supply Chain Management 10.0.49 affecting sales order processing and recurring batch jobs.
  • The issue impacts environments on PQU-1 build 10.0.2790.83 and PQU-2 build 10.0.2790.93; Microsoft has halted rollout of the affected PQU-2 build.
  • Users may be unable to save sales order or return order headers, and recurring sales posting or inventory journal batch jobs may fail.
  • Microsoft has issued a fixed build (10.0.2790.105) and provided workarounds for affected users and batch jobs until the update is installed.
  • Business data is not affected, but admins should remediate failing users/jobs and move to the updated build as soon as available.

Primary Service: D365 Apps
Admin Impact: Medium
User Impact: Medium
Release Start: 02 Nov 2026
Release End: 02 Nov 2026
Services: D365 Apps, Dynamics
Category: Stay informed
Tags: Admin Action, User Adoption

History

11/2/2026 Item Added to Message Center

Microsoft Message

We have identified a code regression in versions 10.0.49 that affects sales order processing and recurring batch jobs. This regression was included in the following proactive quality updates (PQUs):

  • PQU-1 – build 10.0.2790.83
  • PQU-2 – build 10.0.2790.93

In response, we have halted the rollout of PQU-2 build 10.0.2790.93. We have developed a code fix for this issue, which is included in updated build, 10.0.2790.105.

How does this affect me?

Environments on the affected builds can encounter the following error: “A container for table (SalesTable) was packed with more fields than are currently defined on the table and cannot be safely unpacked.” This manifests as impact in the following ways:

  • Some users are unable to save a sales order or return order header.
  • Recurring sales posting batch jobs fail on every run. This includes confirmation, picking list, packing slip, and invoice jobs that were created before the update.
  • Recurring inventory journal batch jobs that were created before the update may also fail. These errors occur for the table InventJournalTable.

Your business data is not affected by this issue.

What action do I need to take?

We will deploy the updated build through the PQU-2 release to address this issue (see release schedule). In the meantime, we have identified workarounds for both affected scenarios.

For users who are unable to save a sales order or return order header, perform the following steps for each affected user.

  1. Go to System administration > Users > Users and select the user. Users can also do this themselves under Settings > User options.
  2. Select User options, then Usage data.
  3. On the All usage data tab, filter Element name on SalesTable2LineUpdatePrompt, select the matching lines, and select Delete. Don’t use Reset usage data.

For recurring batch jobs that fail with the identified error:

  1. Go to System administration > Inquiries > Batch jobs and find the jobs that fail with this error.
  2. Set them to Withhold or delete them.
  3. Recreate them from their original posting page. Don’t use Copy batch job, because it copies the old settings. Don’t reactivate withheld jobs that were created before the update.

If you need to locate the old settings of a failing batch job:

On the affected build, the failing job’s Parameters show the error, so you can’t rely on them. You can still see the job’s description, recurrence, company and batch group on the Batch jobs page, and its class on the Batch tasks grid (for example, SalesFormLetter_Invoice is invoice posting). The information, such as which orders and the posting options, is only in the parameters. To see it:

  • Sandboxes on an unaffected build (10.0.48, a 10.0.49 build before 10.0.2790.56 (for sales jobs), or 10.0.2790.105 or later) that have a copy of production data that was made after the job was created: open the affected job from the copy and select Parameters on the task.
  • Sandbox on the affected build: Temporarily create custom fields through page personalization to access the old batch job parameters. Create 8 fields for SalesTable or 1 field for InventJournalTable, with type Checkbox. After recording the batch job settings, delete the custom fields and apply the changes.

After the hotfix is installed, the old job’s Parameters open again, allowing you to compare the settings and then delete the old job.

For more details, review known issue 1196644. If you need additional assistance with this issue, please contact Microsoft Support and reference this known issue.