Table 7201 "CDS Coupled Business Unit"
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Base Application · Microsoft.Integration.Dataverse · captioned “Dataverse Coupled Business Unit” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Dataverse Coupled Business Unit |
| Access | Internal |
| 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 | Company Id | Guid | Company ID caption | not editable; DataClassification SystemMetadata |
| 2 | Business Unit Id | Guid | Business Unit ID caption | not editable; DataClassification SystemMetadata |
Keys
- Key1: Company Id (clustered)
- Key2: Business Unit Id
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: "CDS Coupled Business Unit"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.