BC Observatoryunofficial, made by waldo
code change · fixPurchasing & Payablesofficial - Microsoftreviewed - checked by Opus

#10368 Bug 614967: Skip mismatched TransferFields in posting

Sales and Purchase posting now skip fields with mismatched types when transferring from source to posted records, allowing posting to continue even when extension fields reuse the same field numbers with different data types.

Open in Claude10368.mdPull request #10368

Pull request · merged into main (BC30) on 2026-08-31 by ChethanT · 22 files (+190 -194), 22 AL · fix · tier official · reviewed (checked by Opus)

What changed

  • TransferFields calls in Sales-Post and Purch.-Post now skip fields with mismatched types
  • Posting continues instead of failing on extension field-number collisions
  • Compatible same-numbered fields are still transferred
  • Mismatched fields keep the target record’s default value
  • Applied to W1 and the localized copies of codeunits 80 and 90
  • Behaviour changes for users or extensions.

AL objects touched

  • Codeunit 90 “Purch.-Post”, Base Application: modified
  • Codeunit 80 “Sales-Post”, Base Application: modified
  • src/Layers/BE/BaseApp/Sales/Posting/SalesPost.Codeunit.al: modified, not in the BC30 snapshot
  • src/Layers/FI/BaseApp/Sales/Posting/SalesPost.Codeunit.al: modified, not in the BC30 snapshot
  • src/Layers/NO/BaseApp/Sales/Posting/SalesPost.Codeunit.al: modified, not in the BC30 snapshot

Context

  • Work items: AB#614967
  • Labels: Team: SCM
  • Systems: purchasing, sales
  • From the description: “posting continues, compatible same-numbered fields are still transferred, and fields whose AL types do not match remain at the target record’s default value”

Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).