| Info | ||
|---|---|---|
| ||
|
...
In standard Business Central the "Package Management" codeunit implements the new Item Tracking Dimension using all eventsubscribers. However, this standard codeunit can only deal with processes known to the base Business Central application and will lack any knowledge of (and support for) processes and fields specific to Mobile WMS. Attempting to post anything set up for Packages Numbers from mobile devices will fail as no Package Numbers is being collected from mobile devices and no values are being transferred though the system to journals etc.
We have created a "framework" (or, pattern) consisting of a rather large number of events (35+) to "fill in the blanks" and implement anything related to Mobile WMS for a new item tracking dimension. Overall these events will be used to:
...
- Verify the Tasklet standard implementation for Packages Numbers is indeed disabled in your solution (no eventsubscribers in your custom code must subscribe to codeunit "MOB Package Management"::OnAfterIsEnabled)
- Download the full Mobile WMS sourcecode from University.taskletfactory.com
- Clone codeunit "MOB Package Management" to your own custom app (changing the object name and object number)
- Remove the "EventSubscriberInstance = Manual;" condition from your cloned codeunit
- Deploy the codeunit to your development server
- Verify that that Package Numbers is now working from the mobile device (note: not every process at the mobile device may work as intended if your existing customizations or vertical solution has changed the processes at mobile devices).
...