Hi,
We are now setting up EMW in our live environement.
beforehand, we have done a number of Pilot setups without much trouble, partcularly setting Roaming (to a UD table)
However, when trying to do this for Live, we get a “Failed to save table” error message.
This is in the mobile app, under Settings->Roaming.
Has anyone else experienced this or aware of the reason behind it?
Thank you
Martyn,
You have to set up a UD table to use to store user settings.
You need to figure out what UD table you were using in pilot or just choose one to use for live and be cool with it.
“Use the Roaming settings to designate UD table to be used to store EMW’s Company and Employee level settings. The options you select in the Settings section of the applications are stored for each Company, and personal information such as custom Material Queue queries and Favorites are stored for each Employee per Company.”
You need to log into the app as a security manager and then go to the settings section of EMW and then go to the roaming section.
Select a table to use to store user settings.
After saving the EMW app will logout. Please ensure all other active users log off so that the changes may take effect.
-This was taken from the EMW guide for 10.2.400.
-Utah
Martyn,
I have a question for you. Did you ever set up a multiscan for any of the menu’s for your Pilot testing?
If so, how did you manage to save those templates when you went live or did you have to re-type them in?
-UTah
Hi utaylor,
Thank you for responding.
I am security manager and I am selecting the same UD table as in Pilot (to keep in consistent with our testing) – However, when I click the Save button, it returns the error.
As mentioned, we did not come about this problem/error when we selected our UD table in our pilot version. This is why I am confused – what could be the reason for this error message?
I might have to install some tracking tool to see what it is calling in epicor and if there is an error response (and if its anymore helpful)
– Lastly, with regards to our configurations, we had a few scanners installed, with their config data in our UD table. I am not sure what you mean by ‘multscan’ but we had a number of scanners/handhelds installed. When we updated Pilot, we saved the json config files in there and put them back in when reinstalled (or new handheld, etc)
Not sure if that answered your question.
M
It kind of answered my question, I just don’t know where to view these config files.
The last thing I guess I would do is try and wipe the data from the app or reset it to factory settings and then try? Do you think there is some weird local cache thing holding it up? Maybe uninstall it and re-install?
These are all just guesses and could have a negative outcome (i.e. wipe a bunch of settings out). I guess I would contact support if all else fails.
Basically - any settings you change in Options/Settings, they are saved in the UD table you set for Roaming.
If you look in the UD table in the database, you will see one of the columns has json text/string. So, if you have setup a handheld with the appropriate settings, you can copy the json an update it directly to the live version. So when you restart the app, those settings will be applied.
Of course, this requires knowledge of connecting and running a SELECT query in the Epicor Database using SQL Server (I am not aware of a dashboard in Epicor that displays a UD table - but it might exist)
So if you have set Roaming for, say, UD40 – then the SELECT query would be something like so:-
select * from Ice.UD40;
I am a software engineer so this task is a pretty mild process for me (and to be careful) - as the json from pilot would then need to be updated on the live version using an UPDATE query – which I only recommend doing if you have experience in this field.
(Again, there could be a dashboard to view data in a UD table)
Besides, I cannot get that far copying json data about because setting a UD table in the Roaming settings… I get that error. 
Thanks for the info.
Yeah I would call support then.
Martyn, is the UD table empty that you are trying to use?
SOLVED: -
I have created a ticket/case in epicare. They spoke to a BISCIT developer, and now the issue has been resolved.
Below is an explanation / solution for me – so it might help someone else in future.
There is a BAQ called BISC_HH_GetCustomSettingsTable. Find out who the Owning Company is.
Log back into EMW under this company and set up Roaming. This fixed the problem.
We now have 2 Companies. During testing (EMW connected to our Pilot environment) the Owning Company for the BAQ was the new Company, so we did not experience this problem.
In Live, the BAQ was under or first/original company.
We only use EMW for the new company (until further notice) so I am not sure how the BAQs were under the new Company… but they were.
Anywat, I am kinda glag it is under the first/original company - as we treat it as our primary, where we ensure our independant BPMs, Functions, etc, are located in.
Anyway – thanks to @utaylor for responding and offering advice. It is appreciated.