BC Observatoryunofficial, made by waldo
codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 9300 "Sync. Looping Helper"

Base Application · Microsoft.Utilities

Open in Claude9300.mdSource on GitHub

Across versions

  1. BC23-30present

Base Application · Microsoft.Utilities · BC23-30 · source at ea08af5e · facts from BC29

Events published

  • OnIsFieldSynchronizationSkipped(TableNo: Integer; FieldNo: Integer; var Skipped: Boolean) (integration)

Event subscriptions

  • CheckTableFieldOnIsFieldSynchronizationSkipped subscribes to Codeunit “Sync. Looping Helper” OnIsFieldSynchronizationSkipped

Procedures

  • SkipFieldSynchronization(var SyncLoopingHelper: Codeunit "Sync. Looping Helper"; TableNo: Integer; FieldNo: Integer)
  • SkipFieldSynchronization(var SyncLoopingHelper: Codeunit "Sync. Looping Helper"; TableNo: Integer)
  • RestoreFieldSynchronization(TableNo: Integer; FieldNo: Integer)
  • RestoreFieldSynchronization(TableNo: Integer)
  • IsFieldSynchronizationSkipped(TableNo: Integer; FieldNo: Integer): Boolean
  • IsFieldSynchronizationSkipped(TableNo: Integer): Boolean

Ask your agent

Procedure bodies are not stored here (D10). 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: "Sync. Looping Helper"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources