Table 5358 "CDS Failed Option Mapping"
Base Application · Microsoft.Integration.Dataverse
Across versionsobsolete removed since 25.0
- BC23-24present
- BC25declaration changed
- BC26declaration changed
- BC27-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | CDS Failed Option Mapping |
| DataClassification | SystemMetadata |
| ObsoleteState | Removed |
| ObsoleteTag | 25.0 |
| ObsoleteReason | Feature OptionMapping will be enabled by default in version 22.0. |
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 | CRM Integration Record Id | Guid | — | TableRelation Table 5331 “CRM Integration Record” (“CRM Integration Record”.SystemId) |
| 2 | Record Id | Guid | — | |
| 3 | Field No. | Integer | — |
Keys
- PK: CRM Integration Record Id, Record Id, Field No. (clustered)
Relations
- CRM Integration Record Id: TableRelation Table 5331 “CRM Integration Record”
Deprecations
- object: Removed 25.0 (#if not CLEANSCHEMA25), “Feature OptionMapping will be enabled by default in version 22.0.”
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: "CDS Failed Option Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.