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

Codeunit 1909 "Media Upload Page Impl."

System Application · System.Device

Across versions

  1. BC23-30present

Neighbourhood 2 connected objects and pages

Page 1909 "Media Upload" (calls, 7 links)Media UploadCodeunit 1910 "File Helper" (calls, 3 links)File Helper

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

Properties

Property Value
Access Internal

Procedures

  • MediaInteractionOnOpenPage(var CameraProvider: DotNet CameraProvider; var MediaUploadAvailable: Boolean)
  • IsAvailable(CameraProvider: DotNet CameraProvider): Boolean
  • SetMediaType(MediaType: Enum "Media Type")
  • SetUploadFromSavedPhotoAlbum(UploadFromSavedPhotoAlbum: Boolean)
  • GetMedia(var TempBlob: Codeunit "Temp Blob")
  • GetMedia(InStream: InStream)
  • HasMedia(): Boolean
  • MediaInteractionOnPictureAvailable(FilePath: Text)

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

  • Page 1909 “Media Upload” (7 calls: CameraProvider::PictureAvailable → MediaInteractionOnPictureAvailable, GetMedia → GetMedia, HasMedia → HasMedia, …)

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

Evidence 1 sources