Page 5374 "New Synthetic Relation Wiz."
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23not present
- BC24added
- BC25-30unchanged
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · captioned “New Synthetic Relation” · BC24-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | New Synthetic Relation |
| SourceTable | Synth. Relation Mapping Buffer |
| PageType | NavigatePage |
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 |
|---|---|---|---|
| BannerStandard | MediaResourceStandardReference | MediaResourcesStandard."Media Reference" |
— |
| BannerDone | MediaResourceDoneReference | MediaResourcesDone."Media Reference" |
— |
| Step0 | Native Dataverse Table | TempSyntheticRelationToCreate."Syncd. Table Name" |
Specifies the native Dataverse table that will be used to create the relation. |
| Virtual Dataverse Table | TempSyntheticRelationToCreate."Virtual Table Caption" |
Specifies the virtual Dataverse table that will be used to create the relation. | |
| Advanced | Virtual Table API Page Id | TempSyntheticRelationToCreate."Virtual Table API Page Id" |
For the selected virtual table, specifies the API page that will be used to browse the related fields. |
| Step1 | FieldsMatchingInstructions | label | — |
| How many fields connect the tables? | NFieldsMatching |
Specifies the number of fields in the native and virtual tables that will be used to create the relation. | |
| FieldsToMatch | Syncd. Field 1 Name | Syncd. Field 1 Name | Specifies the column in the native Dataverse table that will be used to create the relation. |
| Virtual Table Column 1 Name | Virtual Table Column 1 Caption | Specifies the column in the virtual Dataverse table that will be used to create the relation. This must be the logical name of the Dataverse virtual table’s column. | |
| Step2 | We couldn’t find a key for the selected columns of the native Dataverse table selected. A key is being created. Use the action “Refresh” to update the status. | label | — |
| Step3 | ConfirmationTxt | label | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Navigation | Finish | Finish the creation of the synthetic relation. | |
| Next | — | ||
| Back | — | ||
| Advanced | Show advanced settings. | ||
| Refresh | — |
Procedures
SetExistingBCTableRelations(var TempSynthRelationMappingBuffer: Record "Synth. Relation Mapping Buffer")(internal)
Plus 14 local procedures.
Triggers
OnInit, OnOpenPage
Relations
- source table Table 5378 “Synth. Relation Mapping 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 7202 “Synthetic Relations” (2 calls:
NextPage → CreateAlternateKeyForColumns,NextPage → GetExistingAlternateKeyName) - Codeunit 4030 “Client Type Management” (1 call:
LoadTopBanners → GetCurrentClientType)
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: "New Synthetic Relation Wiz."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.