tablePlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Table 9180 "Generic Chart Setup"

Base Application · System.Visualization

Across versions

  1. BC23present
  2. BC242 fields changed
  3. BC25-30unchanged

Neighbourhood 1 connected objects and pages

Table 9182 "Generic Chart Y-Axis" (relates to)Generic Chart Y-Axis

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 · System.Visualization · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Generic Chart Setup
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
2 ID Code[20] — NotBlank
3 Source Type Option — OptionCaption: ,Table,Query
10 Name Text[50] —
11 Title Text[250] —
12 Filter Text Text[250] —
15 Type Option — OptionCaption: Column,Point
16 Source ID Integer —
17 Object Name Text[30] — not editable
20 X-Axis Field ID Integer —
21 X-Axis Field Name Text[80] —
22 X-Axis Field Caption Text[250] —
23 X-Axis Title Text[250] —
24 X-Axis Show Title Boolean —
30 Y-Axis Fields Δ BC24 Integer — FlowField: count(“Generic Chart Y-Axis” where(ID = field(ID))); not editable
31 Y-Axis Title Text[250] —
32 Y-Axis Show Title Boolean —
34 Z-Axis Field ID Integer —
35 Z-Axis Field Name Text[80] —
36 Z-Axis Field Caption Text[250] —
38 Z-Axis Title Text[250] —
39 Z-Axis Show Title Boolean —
40 Chart Exists Δ BC24 Boolean — FlowField: exist(Chart where(ID = field(ID))); not editable

Keys

  • Key1: ID (clustered)

Relations

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: "Generic Chart Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources