| Info | ||
|---|---|---|
| ||
|
...
- 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).
...
All-in-all your customizations to processes and workflows may consist of changes to standard BC, changes to mobile application.cfg, modifed and new DocumentTypes, new mobile Lookup pages etc. Very likely this will make up the major part of your customizations and the most time consuming part of your project. The custom implementation for Package Numbers is just on top of that to make sure the tracking dimension works "behind the scenes". When organizing your project the actual changes to the processees and frontend are best done from other codeunits to make it easier to maintain your custom Package Number implementation (see below).
...