BC Observatoryunofficial, made by waldo
tablePurchasing & Payablesofficial - Microsoftderived - from the source, no model text

Table 9089 "Purch. by Vend.Grp.Chart Setup"

Base Application · Microsoft.Purchases.Analysis

Open in Claude9089.mdSource on GitHub

Across versions

  1. BC23-26not present
  2. BC27added
  3. BC28-30unchanged

Neighbourhood 1 connected objects and pages

Page 767 "Account Schedule Chart List" (pages and codeunits on it)Account Schedule Chart List

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.Purchases.Analysis · captioned “Purch. by Vend. Grp. Chart Setup” · BC27-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Purch. by Vend. Grp. 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
1 User ID Text[132] — not editable; DataClassification EndUserIdentifiableInformation
31 Start Date Date —
41 Period Length Option — OptionCaption: Day,Week,Month,Quarter,Year

Keys

  • PK: User ID (clustered)

Procedures

  • SetPeriod(Which: Option " ",Next,Previous)
  • SetPeriodLength(PeriodLength: Option)

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

Evidence 1 sources