GetProjectionByCriteria User lookup causes TempDB to flood and consume all disk.
Carl_Dorrington
Customer IT Monkey ✭
Using either Postman or Powershell.
When Posting the query below that is given in the Cireson API examples for a User search the query runs and never times out causing the TEMPDB to flood the disk untill no space is left.
{
"Id": "0e1313ab-dc5c-cf9d-d6b0-e2e9835a132a",
"Criteria": {
"Base": {
"Expression": {
"SimpleExpression": {
"ValueExpressionLeft": {
"GenericProperty": "DisplayName"
},
"Operator": "Like",
"ValueExpressionRight": {
"Value": "%Tina%"
}
}
}
}
}
}
This behaviour was the same on our Test and Live system.
Posting a WorkitemID lookup to GetProjectionByCriteria like the example below works with no issue.
{
"Id": "2d460edd-d5db-bc8c-5be7-45b050cba652",
"Criteria": {
"Base": {
"Expression": {
"SimpleExpression": {
"ValueExpressionLeft": {
"Property": "$Context/Property[Type='a604b942-4c7b-2fb2-28dc-61dc6f465c68']/28b1c58f-aefa-a449-7496-4805186bd94f$"
},
"Operator": "Equal",
"ValueExpressionRight": {
"Value": "IR659"
}
}
}
}
}
}
So has the user lookup been depreciated and another method is now used or is there a known configuration issue with this lookup example and instructions on how to fix / configure the system to get it working?
Any help would be appreciated
Carl.
Answers
Hey Carl,
I've never run into this with "GetProjectionByCriteria" in the past. That being said, I typically use that call to look-up work items.
For users, I prefer to use "GetUserList"... more info can be found here: https://support.cireson.com/KnowledgeBase/View/2562#!/
Hope this helps!
Nick