Table 142 "Dispute Status"

Base Application · Microsoft.Sales.Customer · BC24-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 30088 “APIV2 - Dispute Status” (5 Learn pages).

Properties

Property	Value
Caption	Dispute Status

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	Code Δ BC26	Code[10]	Specifies a dispute status code that you can select.	NotBlank; DataClassification CustomerContent
5	Description Δ BC26	Text[100]	Specifies an explanation of the dispute status.	DataClassification CustomerContent
10	Overwrite on hold Δ BC26	Boolean	Specifies if this dispute status should update the on hold value on the corresponding customer ledger entry.	DataClassification CustomerContent

Keys

Key1: Code (clustered)

Relations

lookup page Page 166 “Dispute Status”

Referenced by

8 fields in 6 objects relate to this table (TableRelation or CalcFormula).

Table 112 “Sales Invoice Header”: Dispute Status, Dispute Status Id
Table 5475 “Sales Invoice Entity Aggregate”: Dispute Status, Dispute Status Id
Table 122 “Purch. Inv. Header”: Dispute Status
Table 21 “Cust. Ledger Entry”: Dispute Status
Table 25 “Vendor Ledger Entry”: Dispute Status
Table 686 “Payment Practice Data”: Dispute Status

Pages and codeunits on this table

Page 166 “Dispute Status” (source table)
Page 30088 “APIV2 - Dispute Status” (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: "Dispute Status"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Across versions

Neighbourhood 13 connected objects and pages