How to attach images

Owned by Johannes Sebastian Nielsen
Last updated: Oct 03, 2023
3 min read

Version 4.03

NAV Object version 4.03 or later

For earlier versions you either upgrade or manually Enable Image support in your existing installation

Description

Capture images/photos and attach them to Orders / Lines on any Planned Function.


How to attach images

To Attach an Image to an Order or Order Line,. Select "Attach Images" from the Menu.

You can do this from Orders.


And you can do this from Order Lines.


Select the blue + symbol and take the photo.


Enter a comment describing the image.


You can add more images or select the "Check mark" to save the image(s),


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
set-navserverconfiguration -keyname SOAPServicesMaxMsgSize -keyvalue 60000

NAV
  1. Go to "Microsoft Dynamics NAV Administration"
  2. 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.

Run this powershell command on the server/docker. 

set-navserverconfiguration -keyname SOAPServicesMaxMsgSize -keyvalue 60000


How it works behind the scenes

Images are transferred in two separate requests

  1. Mobile sends an initial request, containing a uniqe ID of the image. (Mobile Doc. Type: PostAdhocRegistration, Registration type: RegisterImage)
  2. 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 experience when handling large image data loads.