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

Each handheld device must be pointed to a device configuration entry in Business Central. To create a device configuration, open the Device Configurations page.

When creating a device configuration, the following fields are important:

When creating Device Configurations, it is not required to have a one-to-one relationship with the devices. A single configuration can be used for all devices if needed. Configurations can be created for any number of reasons (e.g., functional area separation like Receiving/Shipping versus Warehouse operations), per device (e.g., Device1, Device2, etc.), or even per user (e.g., one Configuration for every user).

Splitting configurations often makes sense for but is not limited to, the following reasons:

• Printers are different: If different areas have different printers, it makes sense to use a Device Configuration relevant to that area.
• Batch names conflict: If multiple people would end up using the same batch, it is advisable to split out the configurations so no conflicts occur.
• Setting mismatches per configuration: If a setting or menu needs to be toggled per configuration (e.g., says one device can “post” while another might not be able to).

Software configuration is done by launching the Warehouse Insight application and selecting the Configure menu option. You will be asked for the Configuration password. If you have not changed it, the default value will be “1234”.

The configuration pages are broken down into 6 pages:

• System
• Logins
• Device
• Barcoding
• Logging
• Data

The System Configuration page is used to enter the primary connection details for connecting to Business Central.

The Logins Configuration page is used to toggle the login requirements for connecting to Business Central.

Warehouse Insight supports a few levels of logins. The following table describes these options.

In addition to the basic authentication process occurring during application start-up, using Logins has an impact in other situations such as transaction auditing:

• Using Logins ensures that Device Activity Entries are associated to the username used to log in with.
• Document List lookups are filtered to those that are assigned to the user or are unassigned.
• Opening a document assigns it to the user if the device configuration option is set to do so.

When using Logins, the device prompts the user for their credentials before opening the application.

To configure Warehouse Insight to use Windows logins, complete the following:

1. Set the handheld configuration Login Method to Windows.
2. Create Users in Business Central and generate Web Service Access Keys for each user.

All transactions are processed under the logged in account.

To configure Warehouse Insight to use OAuth logins, complete the following:

1. Set the handheld configuration “Login Method” to OAuth.
2. Create Users in Business Central with a valid windows authenticated password.

All transactions are processed under the logged in account.

To configure Warehouse Insight to use Insight Works’ User Logins the following steps should be taken:

1. Set the handheld configuration “Login Method” to either “Windows” or Oauth.
2. Create Insight Works’ Users in Business Central.

The Insight Works Users do not have to be valid Business Central accounts. All transactions are still executed under the Windows account.  However, any entries made in Business Central have the User ID set to the Insight Works’ User ID used to log in, such as:

• Value Entries
• Warehouse Entries
• Assigned User ID

This option only applies to on premise installations. All transactions are still executed under the Web Service Application Pool account.

To configure Warehouse Insight to not use logins, complete the following:

1. Ensure that the Warehouse Insight Application Pool account is set to a valid Business Central user with appropriate permissions.
   • Assigning the SUPER role is advisable
   • If using Device Licenses, this account should be set to a Device Only User in Business Central
2. Set the handheld configuration Login Method to None.

To configure Warehouse Insight to use User Logins, complete the following:

1. Set the handheld configuration Login Method to User.
2. Create Users in Business Central.

The Users do not have to be valid Business Central accounts. All transactions are still executed under the Windows account. Any entries made in Business Central will have the User ID set to the Insight Works’ User ID used to log in such as:

• Value Entries
• Warehouse Entries
• Assigned User ID

For on premise solutions:

• Ensure that the Warehouse Insight Application Pool account is set to a valid Business Central user with appropriate permissions.
  • Assigning the SUPER role is advisable.
  • If using Device Licenses, this account should be set to Device Only User in Business Central.

The Insight Works’ Users do not have to be valid Business Central accounts. All transactions are still executed under the Web Service Application Pool account. Any entries made in Business Central will have the User ID set to the Insight Works’ User ID used to log in such as:

• Value Entries
• Warehouse Entries
• Assigned User ID

• To configure Warehouse Insight to use Windows logins, complete the following:
  1. Set the handheld configuration Login Method to Windows.
  2. Create Users in Business Central.
  3. Generate Web Service Access Keys for each user.

  For Business Central on premise solutions:

  • Create Users in Business Central:
    1. Ensure the Business Central users have appropriate permission sets applied.
    2. If using Device Licenses ensure the users are set to Device Only User.
  • Modify the Web.Config file to indicate Windows Authentication:
    1. Set AuthenticationMode to 2:

       <setting name="AuthenticationMode" serializeAs="String">
              <value>2</value>
       </setting>

The Device Configuration page is used to manage miscellaneous, optional behaviors on the device.

The Barcoding Configuration page is used to manage how the device receives barcode scans. The barcode wedge options are:

• Android Intent
• Keyboard Prefix/Suffix

Most Android scanners provide a mechanism for signaling barcode scans via Intents. The intent strings/keys will be specific to the device but should look similar to the following:

The scanner can be configured to require that all scans submit a predefined prefix and suffix prior to submitting the barcode data.

For example, if the barcode data scanned was C-100 the device would instead send <C-100> to the Warehouse Insight application (presuming the prefix/suffix was < and >).

The prefix/suffix will be set on the device (exact location/method of doing so dependent on the device). Once done, the same prefix/suffix will be set on the configuration page. The software will listen/look for these special tags and when received know how to correctly interpret/recognize the scan.

This option should be used if your device does not support Scanning Intents.

You can use the devices Camera to scan barcodes by enabling the Use Camera option. When on, you are prompted to enable the Draw over other apps permission. The Camera Scanning button appears over most pages and look like this:

Users can move the button around as needed and the last position will be remembered.

Find the Warehouse Insight application in the list shown and enable the required permission. Once enabled, you can toggle barcode symbologies required. Reducing the amount of enabled symbologies will make the camera scanning more reliable and potentially faster.

The Logging Configuration page is used to change the logging level, clear, and copy the current log file.

The Data Configuration page is used to configure whether Business Central data should be cached on the device as it pertains to item and bin scanning.

The following table indicates what data is cached and frequencies.

• The Clear Cached button is used to delete all cached data entries.
• The Clear Profile button is used to delete the current devices profile data (e.g., column widths, visibility, etc.).

Warehouse Insight supports multiple language options both from Business Central and handheld devices. The following languages are supported:

• • Czech
  • Danish
  • Dutch
  • Dutch (Belgian)
  • English (Australian)
  • English (Canadian)
  • English (New Zealand)
  • English (United Kingdom)
  • English (United States)
  • Estonian
  • Finnish
  • French
  • French (Belgian)
  • French (Canadian)
  • French (Swiss)
  • German
  • German (Austrian)
  • German (Swiss)
  • Icelandic
  • Italian
  • Italian (Swiss)
  • Norwegian
  • Spanish
  • Spanish (Mexico)
  • Swedish

To utilize the Warehouse Insight in alternate languages, you will need to configure the device’s regional setting to the desired language.