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

Codeunit 2506 "Data Out Of Geo. App"

System Application · System.Apps

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Codeunit 2505 "Data Out Of Geo. App Impl." (calls, 4 links)Data Out Of Geo. App Impl.Codeunit 1760 "Data Geo. Notification" (calls)Data Geo. Notification

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

Procedures

  • Add(AppID: Guid): Boolean: Adds an App ID to the list of apps that have data out of the geolocation.
  • Remove(AppID: Guid): Boolean: Removes an App ID from the list of apps that have data out of the geolocation.
  • Contains(AppID: Guid): Boolean: Checks if an App ID is in the list of apps that have data out of the geolocation.
  • AlreadyInstalled(): Boolean: Checks if any of the already installed extensions are in the list of apps that have data out of the geolocation.

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

Evidence 1 sources