Page 5329 "CRM Redirect"
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · captioned “Dataverse Redirect” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Dataverse Redirect |
| SourceTable | CRM Redirect |
| PageType | List |
Procedures
ExtractCRMInfoFromFilters(): TextExtractPartsFromCRMInfo(CRMInfo: Text; var CRMID: Guid; var CRMEntityTypeName: Text)
Triggers
OnFindRecord, OnOpenPage
Relations
- source table Table 5329 “CRM Redirect”
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 5330 “CRM Integration Management” (3 calls:
OnFindRecord → OpenCoupledNavRecordPage,OnOpenPage → IsCDSIntegrationEnabled,OnOpenPage → IsCRMIntegrationEnabled) - Codeunit 5344 “CRM Product Name” (3 calls:
ExtractPartsFromCRMInfo → CDSServiceName,OnOpenPage → CDSServiceName,OnOpenPage → SHORT)
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: "CRM Redirect"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.