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

Table 7203 "CRM Payment Terms"

Base Application · Microsoft.Integration.D365Sales

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-27unchanged
  4. BC281 fields changed
  5. BC29-30unchanged

Neighbourhood 2 connected objects and pages

Page 7210 "CRM Payment Terms List" (pages and codeunits on it)CRM Payment Terms ListCodeunit 7200 "CDS Integration Mgt." (calls)CDS Integration Mgt.

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.Integration.D365Sales · captioned “Dataverse Payment Terms” · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Dataverse Payment Terms
Access Internal
TableType Temporary
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 Option Id Integer — DataClassification SystemMetadata
2 Code Δ BC28 Text[250] Specifies data from a corresponding field in a Dataverse entity. For more information about Dataverse, see Dataverse Help Center. DataClassification SystemMetadata

Keys

  • Key1: Option Id (clustered)
  • Key2: Code

Procedures

  • Load(): Boolean

Pages and codeunits on this table

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "CRM Payment Terms"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources