It's all about the answers!

Ask a question

"prevent adding user owned component" pre-condition failing with other operation

Ratheesh Madathil (1371829) | asked Aug 14 '14, 5:35 a.m.
edited Aug 20 '14, 2:56 p.m. by Stephanie Taylor (24115)
We have enabled:
"prevent adding user owned component" pre-condition for "default role".
But this now behaves strange. If a user tries to acquire a lock on a file or try to "unlock" a file, the team advisor pops up with this error message:
An unhandled exception occurred during "Prevent Adding User Owned Component ".

Wrong type of argument: null

Prevent adding user owned component
Strangely this action has nothing to do with "User Owned component"!!.
When remove this pre-condition, the lock action and unlock action works fine without any errors.

Is somebody else have experienced the same?

Accepted answer

permanent link
Geoffrey Clemm (30.1k33035) | answered Aug 14 '14, 6:26 a.m.
This should be reported as a defect, so the dev team can fix it.
Ratheesh Madathil selected this answer as the correct answer

One other answer

permanent link
Ratheesh Madathil (1371829) | answered Aug 14 '14, 11:30 a.m.
Defect link:

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.