Hello! When trying to use the search projects endpoint for the API, we get a 500 "Unsupported search request filter" error. The same happens if we delete the filter. Any ideas what we may be doing wrong?
Hi Cecilia,
These are examples that you can paste in request body:
//all projects with name containing the string "test"
{"operator":"and","filters":[{"field":"projects(name)","value":"test","operator":"like"}]}
//all projects with name containing the string "test" that have between 2 and 5 tasks
{"operator":"and","filters":[{"field":"projects(name)","value":"test","operator":"like"},{"field":"projects(totalTasks)","value":"2,5","operator":"between"}]}
If you want the result to display only the project ID and project name, you can specify only those fields in the URL (http://hostname/ws-api/v2/projectGroups/search?fields=id,name)
Alternatively, if you want to identify various filtering options, you can:
screenshot #1:
screenshot #2:
Best regards,
Adrian
Hi Cecilia,
These are examples that you can paste in request body:
//all projects with name containing the string "test"
{"operator":"and","filters":[{"field":"projects(name)","value":"test","operator":"like"}]}
//all projects with name containing the string "test" that have between 2 and 5 tasks
{"operator":"and","filters":[{"field":"projects(name)","value":"test","operator":"like"},{"field":"projects(totalTasks)","value":"2,5","operator":"between"}]}
If you want the result to display only the project ID and project name, you can specify only those fields in the URL (http://hostname/ws-api/v2/projectGroups/search?fields=id,name)
Alternatively, if you want to identify various filtering options, you can:
screenshot #1:
screenshot #2:
Best regards,
Adrian
Translate
