Codeunit 46949 "BC14 Item Journal Post Action"

HybridBC14 · Microsoft.DataMigration.BC14Reimplementation · BC29-30 · source at ea08af5e · facts from BC29

Events published

• OnBeforePostMigrationItemJournals(var SkipPosting: Boolean) (integration)
• OnAfterPostMigrationItemJournals(BatchCount: Integer) (integration)

Procedures

• GetDisplayName(): Text[250]
• IsEnabled(): Boolean
• RunAction(): Boolean

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

• Codeunit 46854 “BC14 Migration Error Handler” (2 calls: RunAction → LogError, RunAction → ResolveErrorForRecord)
• Codeunit 23 “Item Jnl.-Post Batch” (1 call: RunAction → (object))
• Codeunit 46866 “BC14 Telemetry” (1 call: RunAction → GetCategory)
• Codeunit 46948 “BC14 Item Ledger Migrator” (1 call: RunAction → GetTemplateName)
• Codeunit 46950 “BC14 Inv. Post. G/L Guard” (1 call: RunAction → SetSuppressInvtPostingToGL)

Implements

• Enum 46884 “BC14 Post Migration Action”

Recent changes

• 2026-08-04 #9663 Migrate customer, vendor and item transactions for BC14 cloud migration (main, BC30, feature, added)

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "BC14 Item Journal Post Action"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.