Page 5328 "CRM Coupling Fields"
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · captioned “Dynamics 365 Sales Coupled Fields” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Dynamics 365 Sales Coupled Fields |
| SourceTable | Coupling Fields Buffer |
| PageType | ListPart |
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 | Field Name | Field Name | Specifies the field’s name in Dynamics 365 Sales. from the table field |
| Value | Value | Specifies the field’s name in Dynamics 365 Sales. from the table field | |
| Integration Value | Integration Value | Specifies the field’s value in Dynamics 365 Sales. from the table field | |
| Direction | Direction | Specifies the direction of data integration. from the table field | |
| Validate Field | Validate Field | Specifies whether to validate the field’s value in Business Central. from the table field |
Procedures
SetSourceRecord(CouplingRecordBuffer: Record "Coupling Record Buffer")
Plus 3 local procedures.
Relations
- source table Table 5327 “Coupling Fields Buffer”
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 5336 “Integration Record Synch.” (1 call:
GetFieldValue → GetTextValue)
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 Coupling Fields"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.