BC Observatoryunofficial, made by waldo
pageSales & Receivablesofficial - Microsoftderived - from the source, no model text

Page 166 "Dispute Status"

Base Application · Microsoft.Sales.Customer

Open in Claude166.mdSource on GitHub

Across versions

  1. BC23not present
  2. BC24added
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Table 142 "Dispute Status" (relates to)Dispute StatusTable 142 "Dispute Status" (pages and codeunits on it)Dispute Status

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.Sales.Customer · BC24-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dispute Status
SourceTable Dispute Status
PageType List
UsageCategory Administration
ApplicationArea Basic, Suite

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group Control Shows ToolTip
Control1 Code Code Specifies a dispute status code that you can select. from the table field
Description Description Specifies an explanation of the dispute status. from the table field
Overwrite on hold Overwrite on hold Specifies if this dispute status should update the on hold value on the corresponding customer ledger entry. from the table field

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: "page", object_name: "Dispute Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources