Table 9175 "Designer Diagnostic"
Base Application · System.Tooling
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · System.Tooling · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| 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 | Operation ID | Guid | — | DataClassification SystemMetadata |
| 2 | Diagnostics ID | Integer | — | DataClassification SystemMetadata |
| 3 | Severity | Enum Severity | Specifies the severity of this diagnostics message. via Page 9196 “Profile Import Diagnostics” | enum Enum 9190 “Severity”; DataClassification SystemMetadata |
| 4 | Message | Text[2048] | Specifies the diagnostics message from the compiler. via Page 9196 “Profile Import Diagnostics” |
Keys
- PK: Operation ID, Diagnostics ID (clustered)
Procedures
Pages and codeunits on this table
- Page 9194 “Designer Diagnostics ListPart” (source table)
- Page 9196 “Profile Import Diagnostics” (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: "Designer Diagnostic"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.