Data sent to the Mobile device once, during login.
Reference Data will always includes static data used by "base functional areas" (i.e. Receive, Pick, Count) and may also include additional static data added from customizations by the partner No Reference Data can be updated at handheld device during a session: It will always require logout/login at device to refresh. For this reason transactional data like Sales Orders should never be provided as Reference Data.
Contents
Reference Data xml file consists of two overall types of static data: Configuration and List Data. Configuration can have one of 3 subtypes: headerConfiguration, registrationCollectorConfiguration or menuConfiguration.
The types are explained below.
For reference, a sample reference data xml file can be seen here: XML example
Menu items included in the main menu. Is always generated based on current data from from Mobile WMS Menu Setup.
Should never need be changed programmatically (and has no Business Central integration events)
List Data (used to populate drop-down boxes)
Location Codes, Return Reason Code, etc.. or customized data
To be used for data that is very unlikely to change during the handheld device session. Transactional data like Sales Orders should never be provided as reference List Data.
Example of headerConfiguration
Key
A predefined key
Base functional Areas (UnplannedCountHeader, PickOrderFilters) or custom name used by a custom page/Tasklet
This XML is automatically converted into table/list data and can be used to populate drop-down boxes by referencing the table and column names in the configuration.