Table 33 "Intercompany Setup Diagnostic"
Base Application · Microsoft.Intercompany.Setup
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Intercompany.Setup · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableType | Temporary |
| DataClassification | CustomerContent |
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 | Id | Code[20] | — | |
| 2 | Description | Text[250] | Description of the intercompany setup issue found. via Page 9097 “IC Setup Diagnostics List” | |
| 3 | Status | Option | — |
Keys
- Key1: Id, Description
Pages and codeunits on this table
- Page 9051 “Intercompany Setup Diagnostics” (source table)
- Page 9097 “IC Setup Diagnostics List” (source table)
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: "Intercompany Setup Diagnostic"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.