Hi Fellows,
Our client is getting below mentioned error whenever they are either creating new Document revision or attaching document to any other window. Its not allowing to move forward.
This error is appearing with every user.
Can anyone help on this..
Regards
Best answer by Mathias Dahl
Perhaps someone though that they could use the #USER# placeholder somewhere in an event action, but that is not supported for what they try to do?
Just as an example, if I had an event action of the type Execute Online SQL, where you can write PL/SQL code, and if I were using '#USER#' as the value for user ID in some procedure call, that would surely fail.
You might be able to find more clues if you enable/open the Debug Console before you try the operation that fails.
Good luck!
+32Hi,
It's really hard to say, but I have two ideas:
1. Someone has been playing around with custom events and made a mistake there.
2. Someone tried to set up Document Defaults per Object (open the Document Basic form and go to the tab with that name, and find all records there) and made a mistake when setting up the rules.
Have a look and report back here.
/Mathias
Thanks
I have checked, there is only one record in Document Defaults per object tab, and it’s not an issue (i have checked).
Regarding Custom event point you made, how can custom event impact this thing (please explain as i have no idea about it) and how to identify this thing as there can be many custom events and actions. Can this error occur even if event is working fine?
Regards
+32Perhaps someone though that they could use the #USER# placeholder somewhere in an event action, but that is not supported for what they try to do?
Just as an example, if I had an event action of the type Execute Online SQL, where you can write PL/SQL code, and if I were using '#USER#' as the value for user ID in some procedure call, that would surely fail.
You might be able to find more clues if you enable/open the Debug Console before you try the operation that fails.
Good luck!
Thanks a ton.
+32Great!
Care to share any details, or might that be embarrassing for someone? … :)
Surely, it will be embarrassing for someone but all i can say is that it was due to an incomplete event which was action enabled.. So i get it corrected and then enabled.
+32That’s good to hear, thanks for reporting back.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
