codeunitAdministration & Setupofficial - Microsoftderived - from the source, no model text

Codeunit 1887 "Environment Cleanup Impl"

System Application · System.DataAdministration

Across versions

  1. BC23-30present

Neighbourhood 1 connected objects and pages

Codeunit 1886 "Environment Cleanup" (calls, 2 links)Environment Cleanup

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.DataAdministration · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property Value
Access Internal
Permissions tabledata Company = r

Event subscriptions

  • OnAfterCopyEnvironmentPerDatabase subscribes to Codeunit “Environment Triggers” OnAfterCopyEnvironmentPerDatabase
  • OnAfterCopyEnvironmentPerCompany subscribes to Codeunit “Environment Triggers” OnAfterCopyEnvironmentPerCompany

Procedures

1 local procedures, no public ones.

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.

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

Evidence 1 sources