Codeunit 9173 "Profile Helper"
Base Application · System.Environment.Configuration
Across versions
- BC23-30present
Neighbourhood 3 connected objects and pages
Base Application · System.Environment.Configuration · BC23-30 · source at ea08af5e · facts from BC29
Procedures
ImportProfileConfigurationPackage(ServerFileName: Text)ReadProfilesFromPackage(var TempProfileImport: Record "Profile Import" temporary; var ImportID: Guid): BooleanImportProfiles(var TempProfileImport: Record "Profile Import" temporary): Guid: Given a read profile package, this function will import the profiles specified from that packageShowProfileDiagnostics(DiagnosticsNotification: Notification)
Plus 4 local procedures.
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 1511 “Notification Lifecycle Mgt.” (1 call:
ShowProfileDiagnostics → SendNotification) - Page 9196 “Profile Import Diagnostics” (1 call:
ShowProfileDiagnostics → (object))
Called by
- Page 9199 “Profile Import Wizard” (2 calls:
OnInitializeStep → ImportProfileConfigurationPackage,OnInitializeStep → ReadProfilesFromPackage)
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: "Profile Helper"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.