Table 2400 "Sync Setup"
SyncBase · Microsoft.Integration.SyncBase
Across versionsobsolete removed since 27.0
- BC23-28not present
- BC29-30present
SyncBase · Microsoft.Integration.SyncBase · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Sync Setup |
| DataClassification | SystemMetadata |
| ObsoleteState | Removed |
| ObsoleteTag | 27.0 |
| ObsoleteReason | The extension is being obsoleted. |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Primary Key | Code[1] | — | |
| 2 | Last Sync Time | DateTime | — | |
| 3 | Current Sync Time | DateTime | — | |
| 4 | Max No. of sync attempts | Integer | — |
Keys
- Key1: Primary Key
Deprecations
- object: Removed 27.0 (#if not CLEANSCHEMA27), “The extension is being obsoleted.”
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). 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: "table", object_name: "Sync Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.