BC Observatoryunofficial, made by waldo
pageIntegration & APIsofficial - Microsoftderived - from the source, no model text

Page 7210 "CRM Payment Terms List"

Base Application · Microsoft.Integration.D365Sales

Open in Claude7210.mdSource on GitHub

Across versions

  1. BC23-26present
  2. BC271 procedures changed
  3. BC28-30unchanged

Neighbourhood 2 connected objects and pages

Table 7203 "CRM Payment Terms" (relates to)CRM Payment TermsCodeunit 5330 "CRM Integration Management" (calls)CRM Integration Management

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

Properties

Property Value
Caption Payment Terms - Dataverse
SourceTable CRM Payment Terms
PageType List
UsageCategory Lists
ApplicationArea 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
Control2 Code Code Specifies data from a corresponding field in a Dataverse entity. For more information about Dataverse, see Dataverse Help Center. from the table field
Coupled Coupled Specifies if the Dataverse record is coupled to Business Central.

Actions

Group Action ToolTip Runs
Processing Create in Business Central Generate the entity from the coupled Dataverse payment terms.
Hide Coupled Payment Terms Do not show coupled payment terms.
Show Coupled Payment Terms Show coupled payment terms.

Procedures

  • SetCurrentlyMappedCRMPaymentTermOptionId(OptionId: Integer)
  • GetRec(OptionId: Integer): Record "CRM Payment Terms" Δ BC27 (internal)
  • LoadRecords()

Triggers

OnAfterGetRecord, OnInit, OnOpenPage

Relations

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: "page", object_name: "CRM Payment Terms List"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources