tableService Managementofficial - Microsoftderived - from the source, no model text

Table 5944 "Troubleshooting Line"

Base Application · Microsoft.Service.Maintenance

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC281 fields changed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Table 5943 "Troubleshooting Header" (relates to)Troubleshooting HeaderPage 5992 "Troubleshooting Subform" (pages and codeunits on it)Troubleshooting Subform

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

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

Properties

Property Value
Caption Troubleshooting Line
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 No. Code[20] — TableRelation Table 5943 “Troubleshooting Header” (Troubleshooting Header)
2 Line No. Integer —
3 Comment Δ BC28 Text[80] Specifies the troubleshooting comment or guidelines.

Keys

  • Key1: No., Line No. (clustered)

Relations

Pages and codeunits on this 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: "Troubleshooting Line"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources