06-23-2009 02:23 AM
Can't figure out why. Security profiles looks OK for me. Anyone who has run into this message before and know how to get rid of it?
06-23-2009 02:28 AM
Between which queues? All?
All operators or?
If any specific, re-create the operator.
Try to add capability word "user" to the operator.
06-23-2009 02:29 AM
You probably have one option in displayoption scm.advanced that says: evaluate(update in $L.env)
06-23-2009 02:51 AM
To create an operator in the command line print operator and fill al necessary data in it
06-23-2009 04:17 AM
It happens when using the drop-down, choosing another queue/view for scm.manage forms, ex scm.manage.problem with display screen scm.advanced.
As far as I have understood the logic, the display option trigger should be GUI option=51(action=getinbox).
It doesn't happen connected as SYSADMIN.
The user I'm using is an operator.
The user capability word didn't help.
The profile should give the operator all needed privilegies on the module.
08-26-2009 04:23 AM
02-09-2010 07:25 AM
type db in command line => ScriptLibrary => viewSetLastChosenView
Change in the line 37 :
Save and Compile and it works.
07-23-2012 02:03 AM
I have modified the code as mentioned but still the error is appearing when refreshing the view after any change is closed.
Can anyone please let me know if there is any other solution.
01-28-2014 03:03 AM
I had a similar problem for a particular operatorID. I solved it by manually adding a row to the ViewDefault table for that operatorID.
Type db in command line
Enter table ViewDefault
Search for name=operatorID (i.e. the login name)
All logins will have an entry for ToDo table, I think.
There may be an entry for incidents table (Interactions) and for probsummary (Incidents), and maybe for cm3r (Changes).
In my case, there was only an entry for ToDo table.
I added an entry for
Table=probsummary, View="Open Incidents assigned to my group"
Table=incidents, View="All Open Interactions"
Now it doesn't give that error for that operatorID.
I don't know why that operatorID was apparently unable to insert into the Viewdefault table.
That operator does now appear to be able to update ViewDefault, for rows that exist already.