BC Observatoryunofficial, made by waldo
codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 5452 "Contoso Analysis"

ContosoCoffeeDemoDataset · Microsoft.DemoTool.Helpers

Open in Claude5452.mdSource on GitHub

Across versions

  1. BC23-28not present
  2. BC29-30present

Neighbourhood 1 connected objects and pages

Codeunit 5536 "Create Analysis View" (calls)Create Analysis View

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.

ContosoCoffeeDemoDataset · Microsoft.DemoTool.Helpers · BC29-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Permissions tabledata “Analysis View” = rim

Procedures

  • SetOverwriteData(Overwrite: Boolean)
  • InsertAnalysisView(Code: Code[10]; Name: Text[50]; AccountFilter: Code[250]; StartingDate: Date; DateCompression: Integer; Dimension1Code: Code[20]; Dimension2Code: Code[20]; Dimension3Code: Code[20])

Called by

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.

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

Evidence 1 sources