Codeunit 2018 "Magic Function"
System Application · System.Text
Across versions
- BC23not present
- BC24added
- BC25-30unchanged
Neighbourhood 3 connected objects and pages
System Application · System.Text · BC24-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
GetPrompt(): JsonObjectExecute(Arguments: JsonObject): VariantGetName(): Text
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 2012 “Entity Text Impl.” (1 call:
Execute → GetFeatureName) - Codeunit 2016 “Entity Text Prompts” (1 call:
GetPrompt → GetMagicFunctionPrompt) - Codeunit 8703 “Feature Telemetry” (1 call:
Execute → LogUsage)
Implements
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: "Magic Function"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.