Codeunit 2676 "Alloc. Acc. Telemetry"

Base Application · Microsoft.Finance.AllocationAccount · BC23-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• LogGeneralJournalPostingUsage() (internal)
• LogSalesInvoicePostingUsage() (internal)
• LogPurchaseInvoicePostingUsage() (internal)
• LogDefinedOverride() (internal)
• GetFeatureTelemetryName(): Text (internal)

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 8703 “Feature Telemetry” (8 calls: LogDefinedOverride → LogUptake, LogDefinedOverride → LogUsage, LogGeneralJournalPostingUsage → LogUptake, …)

Called by

• Codeunit 2677 “Gen. Journal Alloc. Acc. Mgt.” (1 call: HandleBatchPost → LogGeneralJournalPostingUsage)
• Codeunit 2678 “Sales Alloc. Acc. Mgt.” (1 call: HandlePostDocument → LogSalesInvoicePostingUsage)
• Codeunit 2679 “Purchase Alloc. Acc. Mgt.” (1 call: HandlePostDocument → LogPurchaseInvoicePostingUsage)
• Page 2670 “Allocation Account” (1 call: OnOpenPage → GetFeatureTelemetryName)
• Page 2673 “Allocation Account List” (1 call: OnOpenPage → GetFeatureTelemetryName)
• Table 2671 “Alloc. Account Distribution” (1 call: OnInsert → GetFeatureTelemetryName)
• Table 2672 “Allocation Line” (1 call: SaveChangesToAllocationLines → LogDefinedOverride)

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: "Alloc. Acc. Telemetry"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.