codeunitPlatform, DevOps & Performanceofficial - Microsoftderived - from the source, no model text

Codeunit 334 "No. Series Cop. Change Intent"

Business Foundation · Microsoft.Foundation.NoSeries

Across versions

  1. BC23-24not present
  2. BC25added
  3. BC26-30unchanged

Neighbourhood 6 connected objects and pages

Codeunit 336 "No. Series Cop. Tools Impl." (calls, 10 links)No. Series Cop. Tools Impl.Codeunit 2200 "Azure Key Vault" (calls, 2 links)Azure Key VaultCodeunit 349 "No. Series Cop. Nxt Yr. Intent" (calls, 2 links)No. Series Cop. Nxt Yr. IntentCodeunit 389 "No. Series Copilot Telemetry" (calls, 2 links)No. Series Copilot TelemetryCodeunit 8711 "Telemetry" (calls, 2 links)TelemetryCodeunit 324 "No. Series Copilot Impl." (calls)No. Series Copilot Impl.

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.

Business Foundation · Microsoft.Foundation.NoSeries · BC25-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal

Procedures

  • GetName(): Text
  • GetPrompt(): JsonObject
  • Execute(Arguments: JsonObject): Variant
  • SetUpdateForNextYear(IsNextYearIntent: Boolean)

Plus 8 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.

Called by

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: "No. Series Cop. Change Intent"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources