Table 7203 "CRM Payment Terms"
Base Application · Microsoft.Integration.D365Sales
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC281 fields changed
- BC29-30unchanged
Neighbourhood 2 connected objects and pages
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
- Page 7210 “CRM Payment Terms List” (source 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.
- Codeunit 7200 “CDS Integration Mgt.” (1 call:
Load → GetOptionSetMetadata)
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.