Page 346 "Item Picture"
Base Application · Microsoft.Inventory.Item.Picture
Across versions
- BC23-30present
Neighbourhood 6 connected objects and pages
Base Application · Microsoft.Inventory.Item.Picture · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Item Picture |
| SourceTable | Item |
| PageType | CardPart |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Content | Picture | Picture | Specifies the picture that has been inserted for the item. from the table field |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Take | Activate the camera on the device. | |
| Import | Import a picture file. | ||
| Export | Export the picture to a file. | ||
| Delete | Delete the record. |
Events published
OnAfterDeleteItemPicture(var Item: Record Item)(integration)OnAfterTakeNewPicture(var Item: Record Item; IsPictureAdded: Boolean)(integration)OnImportFromDeviceOnAfterModify(var Item: Record Item)(integration)
Trigger event subscribers
- OnAfterActionEvent(ImportPicture): Codeunit 2026 “Item Attr Populate” OnAfterImportPictureAnalyzePicture
Procedures
TakeNewPicture()ImportFromDevice()IsCameraAvailable(): BooleanSetHideActions()DeleteItemPicture()
Plus 2 local procedures.
Triggers
OnAfterGetCurrRecord, OnOpenPage
Relations
- source table Table 27 “Item”
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.
- Codeunit 1907 “Camera” (3 calls:
DoTakeNewPicture → GetPicture,IsCameraAvailable → IsAvailable,OnOpenPage → IsAvailable) - Codeunit 419 “File Management” (2 calls:
ImportFromDevice → DeleteServerFile,ImportFromDevice → UploadFile)
Documented on Microsoft Learn
Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).
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: "page", object_name: "Item Picture"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.