codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 8706 "Telemetry Custom Dimensions"

System Application · System.Telemetry

Across versions

  1. BC23-30present

Neighbourhood 6 connected objects and pages

Codeunit 2301 "Tenant License State Impl." (event subscribers)Tenant License State Impl.Codeunit 9034 "Azure AD User Subscribers" (event subscribers)Azure AD User SubscribersCodeunit 8707 "Telemetry Custom Dims Impl." (calls, 3 links)Telemetry Custom Dims Impl.Codeunit 8712 "Telemetry Impl." (calls, 3 links)Telemetry Impl.Codeunit 2301 "Tenant License State Impl." (calls)Tenant License State Impl.Codeunit 9034 "Azure AD User Subscribers" (calls)Azure AD User Subscribers

Open in the neighbourhood explorer

One hop out, from the extracted relations and call graph. Up to 40 shown; the sections below list them all.

System Application · System.Telemetry · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Public

Events published

Procedures

  • AddCommonCustomDimension(CustomDimensionName: Text; CustomDimensionValue: Text): Add a custom dimension for every telemetry message. Is used in conjunction with
  • GetAdditionalCommonCustomDimensions(ForPublisher: Text): Dictionary of [Text, Text] (internal)
  • AddAllowedCommonCustomDimensionPublisher(Publisher: Text) (internal)
  • AddCommonCustomDimension(CustomDimensionName: Text; CustomDimensionValue: Text; Publisher: 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 8707 “Telemetry Custom Dims Impl.” (3 calls: AddAllowedCommonCustomDimensionPublisher → AddAllowedCommonCustomDimensionPublisher, AddCommonCustomDimension → AddCommonCustomDimension, GetAdditionalCommonCustomDimensions → GetAdditionalCommonCustomDimensions)

Called by

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

Evidence 1 sources