Sudden error message: This set of parameters is not allowed on WorkItemHierarchy-Report
Officially Answered
Dear Support,
I did create an individual WorkItemHierarchy Report. Starting this week (probably this year?) I get the following message:
This set of parameters is not allowed, to lear ... please follow link
However the content of the link does not help.
Please find the export of the report below:
{"type":"HierarchyTable","id":"","title":"Time Registration Hierarchy","subTitle":"","w":4,"h":3,"odataVersion":"v3.0","endpoint":"workItemsHierarchy","query":"$orderby=TrackedTotal desc&$top=10000","hierarchyField":"System_Id","childrenEndpoint":"workItemsHierarchy","childrenQuery":"({hierarchyField})/Children?{query}","hierarchyType":"workItems","columns":[{"field":"System_Id","title":"ID","formatter":"WorkItemId","width":100},{"field":"System_Title","title":"Title","formatter":"","width":250},{"field":"Microsoft_VSTS_Scheduling_OriginalEstimate","title":"Budget","width":80},{"field":"Microsoft_VSTS_Scheduling_RemainingWork","title":"Remaining","width":80},{"field":"TrackedItselfBillable","title":"Billable","width":80,"formatter":"TimeLength"},{"field":"TrackedTotal","title":"Tracked","width":80,"formatter":"TimeLength"}],"autoSubtitle":true,"timeframeFilter":{"from":null,"to":null,"filterType":"NoFilter"},"y":0,"x":0}
-
Hello,
Thank you for reaching out to us.
Calculating these fields - "TrackedItself", "TrackedTotal", "TrackedItselfBillable", "TrackedTotalBillable" - is a heavy operation, so retrieving them can take a considerable amount of time.If a user runs a query that returns the first 100 rows ordered by TrackedItself field. Only 100 rows are requested, but the application has to calculate TrackedItself for the whole organization's work items based on all worklogs that were ever tracked to just sort them.
Right now, it is impossible to sort or filter by a calculated field based on all data for all times. If such a filter or order is added to a query, then using the worklogsFilter becomes required to limit the number of worklogs for calculation, and this is what we suggest that you use. You can learn more about the worklogsFilter here.
Here are some examples:
// this query is allowed because it doesn't use sorting or filtering by a calculated field
https://your_org_name.timehub.7pace.com/api/odata/v3.0/workitems?$select=System_Id,System_WorkItemType,TrackedItself&$filter=System_TeamProject eq 'My project'
// following queries will throw an exception
// because worklogsFilter is not used and values are calculated basing on all worklogs
https://your_org_name.timehub.7pace.com/api/odata/v3.0/workitems?$select=System_Id,System_WorkItemType,System_TeamProject,TrackedItself&$filter=System_TeamProject eq 'My project'&$orderby=TrackedItself desc
https://your_org_name.timehub.7pace.com/api/odata/v3.0/workitems?$select=System_Id,System_WorkItemType,System_TeamProject,TrackedItself&$filter=System_TeamProject eq 'My project' and TrackedItself ge 3600
// these queries are allowed -
// although they use filtering or sorting by a calculated field
// those calculations are based on worklogs filered by dates,
// so TrackedItself would contain sums of worklogs from a specified month only
https://your_org_name.timehub.7pace.com/api/odata/v3.0/workitems?$select=System_Id,System_WorkItemType,System_TeamProject,TrackedItself&$filter=System_TeamProject eq 'My project'&$orderby=TrackedItself desc&worklogsFilter=Timestamp ge 2020-10-01 and Timestamp lt 2020-11-01
https://your_org_name.timehub.7pace.com/api/odata/v3.0/workitems?$select=System_Id,System_WorkItemType,System_TeamProject,TrackedItself&$filter=System_TeamProject eq 'My project' and TrackedItself ge 3600&worklogsFilter=Timestamp ge 2020-10-01 and Timestamp lt 2020-11-01Best regards,
Vanja
Please sign in to leave a comment.
Comments
3 comments