Table 5327 "Coupling Fields Buffer"
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23present
- BC24declaration changed
- BC25-27unchanged
- BC285 fields changed
- BC29-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · captioned “Coupling Field Buffer” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Coupling Field Buffer |
| 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 | Field Name Δ BC28 | Text[50] | Specifies the field’s name in Dynamics 365 Sales. | DataClassification SystemMetadata |
| 2 | Mapped Field Name | Text[50] | — | DataClassification SystemMetadata |
| 3 | Value Δ BC28 | Text[250] | Specifies the field’s name in Dynamics 365 Sales. | DataClassification SystemMetadata |
| 4 | Integration Value Δ BC28 | Text[250] | Specifies the field’s value in Dynamics 365 Sales. | DataClassification SystemMetadata |
| 6 | Direction Δ BC28 | Option | Specifies the direction of data integration. | OptionCaption: Bidirectional,ToIntegrationTable,FromIntegrationTable; DataClassification SystemMetadata |
| 8 | Validate Field Δ BC28 | Boolean | Specifies whether to validate the field’s value in Business Central. | DataClassification SystemMetadata |
Keys
- Key1: Field Name, Mapped Field Name (clustered)
Pages and codeunits on this table
- Page 5328 “CRM Coupling Fields” (source table)
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: "table", object_name: "Coupling Fields Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.