Page 6250 "Data Sync Status"
Base Application · System.Environment.Configuration
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Data Sync Status |
| PageType | Document |
| UsageCategory | Administration |
| ApplicationArea | All |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Content | Data Migration Status | part Page 1795 “Data Migration Overview Part” | — |
| Migration Errors | part Page 1796 “Data Migration Error Part” | — | |
| Posting Errors | part Page 1796 “Data Migration Error Part” | — |
Events published
OnSkipPostingErrors(var SkipPostingErrors: Boolean; JournalBatchName: Text)(integration)
Procedures
ParsePosting()SetMigrationVisibility(IsMigration: Boolean)
Plus 1 local procedures.
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.
- Report 6250 “Auto Posting Errors” (1 call:
PostingErrors → (object))
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "page", object_name: "Data Sync Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.