BC Observatoryunofficial, made by waldo
codeunitAL Developmentofficial - Microsoftderived - from the source, no model text

Codeunit 2505 "Data Out Of Geo. App Impl."

System Application · System.Apps

Open in Claude2505.mdSource on GitHub

Across versions

  1. BC23-30present

Neighbourhood 3 connected objects and pages

Codeunit 2506 "Data Out Of Geo. App" (calls, 4 links)Data Out Of Geo. AppCodeunit 457 "Environment Information" (calls)Environment InformationPage 2510 "Marketplace Extn Deployment" (calls)Marketplace Extn Deployment

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

Properties

Property Value
Access Internal

Procedures

  • Add(AppID: Guid): Boolean
  • Remove(AppID: Guid): Boolean
  • Contains(AppID: Guid): Boolean
  • AlreadyInstalled(): Boolean
  • CheckAndFireNotification(AppID: Guid) (internal)

Plus 1 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

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: "Data Out Of Geo. App Impl."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Evidence 1 sources