tableIntegration & APIsofficial - Microsoftderived - from the source, no model textobsolete - removed

Table 5333 "Coupling Field Buffer"

Base Application · Microsoft.Integration.Dataverse

Across versionsobsolete removed since 25.0

  1. BC23present
  2. BC24declaration changed
  3. BC25declaration changed
  4. BC26declaration changed
  5. BC27-30unchanged

Base Application · Microsoft.Integration.Dataverse · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Caption Coupling Field Buffer
DataClassification CustomerContent
ObsoleteState Removed
ObsoleteTag 25.0
ObsoleteReason This table is no longer used. Use Coupling Field Buffer table instead.

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 Text[50] — DataClassification SystemMetadata
3 Value Text[250] — DataClassification SystemMetadata
4 Integration Value Text[250] — DataClassification SystemMetadata
6 Direction Option — OptionCaption: Bidirectional,ToIntegrationTable,FromIntegrationTable; DataClassification SystemMetadata
8 Validate Field Boolean — DataClassification SystemMetadata

Keys

  • Key1: Field Name (clustered)

Deprecations

  • object: Removed 25.0 (#if not CLEANSCHEMA25), “This table is no longer used. Use Coupling Field Buffer table instead.”

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

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 Field Buffer"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources