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

Codeunit 510 "Change Log Entry - Delete"

Base Application · System.Diagnostics

Across versions

  1. BC23present
  2. BC24declaration changed
  3. BC25-30unchanged

Neighbourhood 2 connected objects and pages

Table 405 "Change Log Entry" (relates to)Change Log EntryReport 510 "Change Log - Delete" (calls)Change Log - Delete

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.

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

Properties

Property Value
Access Internal
TableNo Change Log Entry
Permissions TableData “Change Log Entry” = rd

Triggers

OnRun

Relations

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: "Change Log Entry - Delete"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources