I'm not sure what you are talking about. This used to be an issue, but I haven't seen it happen for a long time. Maybe you could explain what version that you had this with, and exactly what is happening.
Every build of 2014, 2015, and 2016. I don't remember before that. Is anyone else experiencing this? The Options settings get changed and the personal directory gets cleared out and I have to start all over again each time.
2 of 2 people found this helpful
Yes, I've seen this for years. If it's been fixed, I don't know about it. As a matter of course, I set aside a copy of the \speller\ sub-folder off the Sysdir and restore it after updates are complete.
Bob et al.,
I apologize as this is a currently open issue with our Development Team. It does not happen for every deployment every time; for this reason it has been a particularly slippery one.
You may want to use the Self Service Portal to open an incident so your customer can be added to the issue:
This is RM issue #146983 TLX files do not retain custom added words after upgrade.
There is also Knowledge Article 19581 - Speller / TLX files are not retained during an upgrade of GoldMine. The user's speller files are lost after an upgrade of GoldMine
Essentially the workaround is as Doug suggested; per the article:
"Prior every upgrade take a backup of the Speller folder and after the upgrade copy back the missing files and if applicable reconfigure the settings, otherwise replace the whole Speller folder content from the backup"
We certainly apologize about the inconvenience.
I do the same thing!
Hi Jason, I can't recall a single upgrade that the speller did not get wiped out. I've just added it's recovery to my upgrade checklist. Since we would never do an upgrade without a backup, it's recovery is annoying but not that difficult. I guess I fell into that "already reported" trap. We will start to report it from now on.
I'm not a programmer so I may be way off base here.
When you point the install to an existing GoldMine installation it seems that the process could look for an existing Speller folder and if found skip over it and not replace it. Isn't it already doing that for other folders; Mailbox, Reports, Sync, Template, TmpLinks?
Albert, yes please open incidents via the normal channels and reference RM #146983. I would disagree with " "already reported" trap". I think this more falls in a bucket of difficult long standing issues that are being worked on but because they are inconsistent and not reproducible all the time they have not been resolved.
Bob - I am no programmer either and though some report this happening every time many others do not. This may be because more deployments are using Outlook or that the speller is not used. I am sure if the issue were that easy regarding the code it would be fixed. Something tells me though this is not the case.