pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 30088 "APIV2 - Dispute Status"

APIV2 · Microsoft.API.V2

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 6 connected objects and pages

Table 142 "Dispute Status" (relates to)Dispute StatusCreate disputeStatus (Learn pages)Create disputeStatusDelete disputeStatus (Learn pages)Delete disputeStatusdisputeStatus resource type (Learn pages)disputeStatus resource typeGet disputeStatus (Learn pages)Get disputeStatusUpdate disputeStatus (Learn pages)Update disputeStatus

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.

APIV2 · Microsoft.API.V2 · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Extensible false
SourceTable Dispute Status
PageType API

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
Group Id Rec.SystemId —
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

Relations

Documented on Microsoft Learn

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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

Evidence 6 sources