![[ Tips & Tricks ] Kinetic Warehouse Persist Settings after Factory Reset](https://media.licdn.com/dms/image/v2/C4E12AQHJmYrk_0Ttgg/article-cover_image-shrink_720_1280/article-cover_image-shrink_720_1280/0/1639485946946?e=2147483647&v=beta&t=aI59_5yL_QlKIgWBsnLDlvQbtEB6YBlKU9BwGkGJzAw)
[ Tips & Tricks ] Kinetic Warehouse Persist Settings after Factory Reset
I asked Epicor's lead on Epicor Kinetic Warehouse, if EKW can persist settings after a factory reset. I knew in August 2021 that you could login and select your UD Table and it will pull your settings. But you would have to do that every time you bought a new device or factory reset an existing device. I wanted the user to get the settings upon first-ever login on a brand new Handheld. The answer I received was "No, not at this time but please email us it sounds like a good idea".
It turns out Biscit thought about it before Epicor acquired their application, and they have it built in, however it is no where to be found in any User Guides. I looked at the Biscit Guides as well as the ones available on EpicWeb at that time. I believe the Epicor Lead was unaware of this capability, or he misunderstood me. Nonetheless, it is very easy to configure.
If anyone finds "how roaming settings should be configured" mentioned in any of the official guides, let me know.
It is only mentioned in a KB Article (the only place I found a mention of it). https://epiccare.epicor.com/epiccare?id=epiccare_kb_article&sys_id=34aa85d9dbca1858a587ef070596192c
How to Persist EKW Application Settings?
When you login to the Epicor Kinetic Warehouse application, it will query 2 BAQs BISC_HH_GetCustomSettingsTable & BISC_HH_GetEmptyTables and if they don't exist it will import them. Be sure that you are logging in with a security manager account the first time ever, and if you have not, then you can download the BAQs from the KB article mentioned above, and configure them.
After your first login to EKW, go to Settings -> Roaming and select your roaming table. It will modify the BISC_HH_GetCustomSettings BAQ for you.
If you don't have a device present you can still configure a table by modifying the BISC_HH_GetCustomSettingsTable BAQ. Edit the Calculated field with your desired UD table where you would like to store your Roaming Settings.
Now your company and user settings will be stored in the UD table of your choice and be applied after first login on any new device. You can edit the application settings for all users anytime as long as you login with an account that is a security manager.
To Recap:
It is very important that Epicor continues to consider Enterprise level of deployments and configuration for the applications and products they sell. If you are working on the helpdesk and swapping or configuring 10 handhelds daily, having to manually configure each of the 100s of checkboxes would be time consuming and prone to human error. In EKW specifically, it is executed very well. Please continue this practice.
How to Persist Handheld Settings?
When it comes to Handheld device settings you can look into Microsoft Intune and consult the Zebra's DataWedge Enterprise deployment guides.
Clone Settings to other Companies?
If you want to migrate settings from Development to Production or clone them to other companies in a multi-company environment, simply retrieve the UD table values and you can DMT them into Production.
Haso, thanks for the post and positive comments. There is Roaming Settings section In the User Guide available at : https://epicweb.epicor.com/doc/Docs/EpicorMfgWirelessWarehouse_UserGuide.pdf#search=EMWW user guide Admittedly, it is quite brief and technical detail about the implementation, BAQ names etc are not included here. Just as an FYI, Biscit still owns and?actively develops and extends functionality of the EKW (Epicor Kinetic Warehouse) product and the mechanism of storing the Roaming setting has not changed since the original release. Settings configured by Security Managers are stored in selected Epicor DB UD table per Company and application version. These settings are automatically copied over to a new version after version upgrade. The settings are retrieved and applied each time user (Security Manager or “regular” user) logs into the application. This mechanism seems to be working well and we have not had many issues reported regarding this functionality. Resetting the device does not affect the data stored in Epicor DB UD table, similarly connecting a new device does not affect the saved configuration. Therefore, if a new device or reset device running EKW connects to an Epicor instance in which the Roaming settings have been configured those settings will be applied to the connecting devices at the log in time. Also to note, we now have support for MDM (Mobile Device Management) using tools like Soti, with configuration parameters for things like the licence code and the server address, so even these elements do not need to be entered on each device if using an MDM and supporting a large number of devices. Along with new functionality and tweaks with every release, we also have some new and exciting features planned for 2022...!!
Epicor ERP Expert / Software Engineer
3 年One Undocumented Feature I have been using in early 10.2 builds is something Jose Gomez showed me. That is simply using an Updatable BAQ (UBAQ) like an Epicor Function. Tucking away the code in the Advanced BPM section of a UBAQ and then invoking that UBAQ from Customizations & BPMs.