This document is intended to provide an overview of the basic usage and capabilities of the Warehouse Insight application.

This section will describe those general concepts and subsequent sections will detail individual modules. Where applicable the individual modules will override the general behavior described here.

The initial interface is broken into several applications. The typical default installation will look like this:

The “Item Inquiry” application provides information about Items the system.

The “Bin Inquiry” application provides information about Bins the system.

The “Count” application is used to perform inventory counts. The application acts as an interface for the “Advanced Inventory Count” product and is an optional purchase. If you have not purchased the product you may instead use the “Basic Count” application.

The “Basic Count” application can be used to perform inventory counts, when the Advanced Inventory Count application has not been purchased. The Basic Count primarily acts an interface around the Physical Inventory Journal. If the Advanced Inventory Count application has been purchased it should be used instead of the Basic Count.

The “Receive” application is responsible for handling inbound transactions.

The “Put-Away” application is responsible for handling Inventory Put-aways and Warehouse Put-aways.

The “Ad-Hoc Movements” application allows users to move Items between Bins.

The “Directed Movements” application is responsible for handling Inventory Movements and Warehouse Movements.

The “Pick” application is responsible for handling Warehouse and Inventory Pick transactions.

The “Ship” application is responsible for handling outbound transactions.

The “Consumption” application allows users to record Consumption against Production Orders.

The “Output” application allows users to record Output against Production Orders.

The “Assembly Order” application is responsible for processing mainly “Assemble to Stock” orders with limited support for “Assemble to Order” documents.

The “License Plates” application is responsible for managing License Plates independently of any specific document.

The “Scratchpad” application is an “Offline Application” and can be used to gather various information.

There are two primary configuration points that need to be set up prior to utilizing the device software. Business Central Device Configuration Code & Software Configuration

To get the most out of Warehouse Insight, you must keep [...]

The following describes how to set up PrintNode and configure Business Central to let you print from your handheld to a local printer.

Files Attached: FalconX4-Wifi, FalconX3-Wifi

When scanning barcodes in a noisy environment it can be hard to hear the notification indicating that the scan was successful. To get the maximum audio notification there are 2 places to check audio settings on the handheld.

To allow the Warehouse Insight web service to work with NTLM, you just need to make one small change to the ‘web.config’ file.

A handheld scanner needs to be provisioned before it can use Warehouse Insight. The Warehouse Insight desktop client should already be configured and functional before configuring scanners.

Warehouse Insight extension has to be installed and Warehouse Insight Setup Wizard has to be completed.

If a scanner goes into power save mode or drops the wifi connection the Warehouse Insight app will need to reset and log back in each time.

Warehouse Insight services are configured for each instance of Business Central, and so when additional services are required for Dev/Test/Production they can be set up as shown below.

A handheld scanner needs to be provisioned before it can use Warehouse Insight.

Issue: Reclass (bin to bin move) entries being overwritten by another scanner. Cause: Multiple scanners using the same Device/PDA Configuration Code, where a Reclass Journal Batch has been hardcoded.

You can add a custom image to the home screen of the Warehouse Insight application on your device. This can be useful if you want to display corporate branding information, or if you have multiple device configurations and you want to see which configuration your device is using at a glance, without having to go into the configuration menu on the device.

The App Designer provides a simple way to add new apps to Warehouse Insight, or to extend existing apps with new business logic.

To get started creating Applications you should already have the prerequisite components in place and access to a test device.  This section will describe the configuration and walk through creating a very simple “Hello World” application.

The designer events are generally triggered either by actions taken by users (scanning barcodes, pressing menus, etc.) or by specific processes internal to the application framework (opening or closing an application, loading data, etc.).  There should only be one instance of an event per application and should only be added to the application as needed.

The designer interactions are generally user interfaces designed to show information to the user or to gather feedback (input dialogs, quantity dialogs, message boxes, etc).  The interface presented for the most part cannot be further customized but may present slightly differently depending on the operating system running Warehouse Insight.

The designer actions generally do not show input/dialog controls to the user but are instead intended to facilitate the process logic between elements.

The designer context blocks are primarily responsible for putting data into the global context so that they can be referenced by the application blocks or Business Central.

The designer variable blocks serve as defined variables in the application to make it easier to work with data and control process logic.

The designer logic blocks are used to control process flow through the application. The following sections will outline each available action and provide a brief example of how the action can be used.

PDA Menus are integral to the Application Development process.  Menus define their interactions with Applications via the “Standard Action” property.  Each of the standard actions are briefly described below where they directly pertain to Application interactions.

Inevitably when designing an application you will need to handle data requests in NAV.  This document has provided examples of NAV code where required.

In some cases, users of Warehouse Insight will want to be able to add comments to documents from their mobile devices.  This article will walk through the steps and code required to add a Purchase Order comments from the device.

This article will walk through the steps and code required to display Purchase Order comments when a Purchase Order is opened.

In some cases, users of Warehouse Insight will want to be able to take pictures and add that picture to the document from their mobile devices. This article will walk through the steps and code required to add capture a picture on a Sales Order from the device and add it as an attachment to the document.

There are times where you may need to create custom handling for documents, images, or signatures captured by the handheld device. Warehouse Insight 2.2 provides a mechanism to create a custom handler for files sent to Business Central from the handheld device.

In some cases, users of Warehouse Insight will want to be able to invoice documents in addition to shipping when posting.  This article will walk through the steps and code required to Ship and Invoice a Sales Order.

There are three important steps in overriding a base event. Here is an example of how you would remove the print dialog after creating a License Plate in the WHI Ship app. 

This article will describe the process of building and consuming a simple offline application to capture inventory count information.

This article will describe the process of extending the Quantity dialog in Warehouse Insight to capture additional information.

FactBoxes are a feature of Dynamics 365 Business Central that provides users with helpful information about the page being viewed. Now, this concept is being brought to Warehouse Insight 2.5.

There are several settings in Inventory Setup and General Ledger setup that need to be reviewed when multiple users are required to post shipments and other inventory transactions simultaneously.

This is due to a non-specified journal batch for the scanner for Reclass entries.

Warehouse Insight fails on "Padding is invalid and cannot be removed."

During training or demos you may wish to show your device screen on your computer’s monitor or over a web meeting. There are applications for both Android and Windows devices to support this.

Microsoft is removing the ability to log in using a Web Service Access Key in the Business Central 2022 wave 1 (Business Central 20) SaaS. You will not be able to use Warehouse Insight or Shop Floor Insight after Microsoft updates your system if you have not switched to OAuth.