| Noteinfo | ||
|---|---|---|
| ||
| ||
NAV Object version 4.03 or later .For earlier versions you either upgrade or manually Enable Image support in your existing installation |
Description
| Excerpt |
|---|
Capture images/photos and attach them to Orders / Lines on any Planned Function. |
...
| Table of Contents | ||||
|---|---|---|---|---|
|
How to attach images
To Attach an Image to an Order or Order Line,. Select "Attach Images" from the Menu.
...
The image(s) has been saved.
How to view attached images
You can now see that the images have been attached. And it is possible to fetch the attached images again by selecting the action “Attachments”.
A "Clip" symbol is displayed if images are attached.
Select "Attachments".
A list of attached images is then displayed.
How to view attached images from BC
Images are stored in the Mobile WMS Media Queue.
- Go to the Mobile WMS Media Queue page.
- Select an entry.
How to Enable
Update Mobile config setup
- Ask Tasklet Support to be upgrade to latest mobile configuration or add the following:
- Make sure you are using Mobile WMS Extension version 5.14 or later or NAV version 4.04.
Service tier setup
BC On-Prem / DOCKER
- Run this PowerShell command
| Code Block |
|---|
set-navserverconfiguration -keyname SOAPServicesMaxMsgSize -keyvalue 60000 |
NAV
- Go to "Microsoft Dynamics NAV Administration"
- Set the "Max Message Size" = 65535.
Error: No Images are sent to BC
- Entries exist but no images are stored in Media Queue
- No "PostMedia" requests are made
- The Mobile log says: "Could not upload media"
Solution
The SOAP Message size is too small.
...
set-navserverconfiguration -keyname SOAPServicesMaxMsgSize -keyvalue 60000
How it works behind the scenes
Images are both transferred and requested to/from BC ad-hoc.transferred in two separate requests
- Mobile sends an initial request, containing a uniqe ID of the image. (Mobile Doc. Type: PostAdhocRegistration, Registration type: RegisterImage)
- Mobile sends a second request, containing the unique ID and the image date. (Mobile Doc. Type: PostMedia, Registration type: Type: Image)
This is done to provide the mobile user with a real-time graphic experience even when handling large image data loads.This means that you may experience a small delay in when images are display and stored.Technically speaking: "GetMedia" and "PostMedia" mobile requests are sent independently from the "GetOrderLines" and "PostAdhocRegistration-RegisterImage".