The answer may be a yes. It depends. In my instances (yes, numerous), I have lost the pcode settings for a given model. It usually starts as an edit to a model template and then you do a save. The initial save message is success in green at the top of the screen immediately followed by a red error message.
When this occurs, you can usually go to the operation log and you will see an entry of delete all custom configurations for template X. If you then look at the template following the loss, you may see a -1 in place of the VPMK name function type (line, forward, call park, BLF, etc.).
if you have the same issue(s) as described above, then DO NOT MAKE ANY EDITS TO ANY OTHER TEMPLATES. These will likely also become compromised.
I have reported this 4 different times to no avail and no response as to how it occurred, how might I have caused it and what can I do to prevent it and more to the point, where is the delete all custom config button so clearly listed in the op log as I certainly don’t want to press that again.
The claim is that the config database is corrupted and the only way to recover is a full factory reset and restore or manual rebuild. When it first occurred, I did not recognize it for what it was and the kicker is that if you do backups on a scheduled basis, the issue may be in the backup. Only as I had a few more UCMs do this did I become wiser about the situation.
I have since given up on a resolution and no answers or suggestions were forthcoming…sorry to say as I kept submitting tickets and not getting anywhere. Some of the systems were quite new, so I do not believe it should have been a non-volatile memory issue, but maybe.