Developer's Overview

This document will give you a general overview of the objects deployed by iDynamics Warehouse, so that you can extend the app.

If you have any questions regarding how to customize the app that is not answered in this manual, please do not hesitate to get in touch with us through our support portal.

Tables

iDynamics Warehouse adds three tables to Business Central that will be used to receive all data sent by the mobile app:

  • IDPWHS Read Buffer: scans and information of every document line handled in the app.
  • IDPWHS Reclass. Buffer: when an employee moves an item between bins, this table stores all movements before they are processed using an item reclassification journal.
  • IDPWHS Inventory Buffer: inventory counts. All information read by the users, before it is applied to an inventory journal.

When users send data from the mobile app, the information is stored in these tables, and it is only processed when the document is posted, the ad hoc movement is finished, or the inventory count is applied. This means that, if any errors were raised when posting one of the documents, for example, all data will be stored in these tables (writing to the tables and posting is always done in different transactions), so that Business Central can check and fix any problems.

Each of these three tables have an equivalent Archive XXX table (XXX being the name of the original table) where entries will be stored after they have been processed.

Events

The following codeunits are in charge of processing the different documents handled by the application, and trigger different events when actions are launched from the application, or when the different documents are posted/registered (to apply the readings received).

  • IDPWHS Inbound Transfer Header. Events associated with the receipt of transfer orders.
  • IDPWHS Outbound Transfer Hdr. Events associated with the shipment of transfer orders.
  • IDPWHS Purchase Header. Events associated to receipt headers.
  • IDPWHS Sales Header. Events associated to receipt headers.
  • IDPWHS Whse. Activity Header. Events associated to receipt headers.
  • IDPWHS Whse. Receipt Header. Events associated to receipt headers.
  • IDPWHS Whse. Shipment Header. Events associated to receipt headers.

Each of these codeunits includes the following events:

  • OnBeforeLockUnlock. Executed when an attempt is made to lock or unlock a document from the mobile application.
  • OnAfterLockUnlock. Executed after locking/unlocking a document.
  • OnBeforePostFromDevice. Executed when a document is confirmed from the mobile application. This action will apply the readings and post the document, or mark it as finished, depending on the configuration of the warehouse employee.
  • OnBeforeProcessReadBuffer. Executed before applying the readings to the document. Readings are applied both when the document is finished from the mobile application and at posting of the document (which could be different times depending on the warehouse employee's configuration).
  • OnAfterProcessReadBuffer. Parallel to the previous one, it is executed once the readings have been applied to the document.
  • OnBeforeArchiveQuestionnairesAnswers. After posting a document, its answers are archived and associated to the posted document. This event is executed before performing this action.
  • OnAfterArchiveQuestionnairesAnswers. Executed after archiving the answers.

In addition to the above events, there are events to customize printing from the mobile application.

Remember, however, that you can request new events through our support portal.