Codeunit 5367 "CRM Update Unit Group Mapping"
Base Application · Microsoft.Integration.D365Sales
Across versions
- BC23-30present
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Integration.D365Sales · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| TableNo | Job Queue Entry |
| Permissions | TableData Item = r, TableData Resource = r, TableData “Unit Group” = rimd |
Triggers
OnRun
Relations
- runs on Table 472 “Job Queue Entry”
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” (2 calls:
OnRun → UpdateItemUnitGroup,OnRun → UpdateResourceUnitGroup)
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: "codeunit", object_name: "CRM Update Unit Group Mapping"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.