Is there a bug which could cause inconsistent data retrieval using the RTC REST API (to get Project Team Members)
I'm using the REST API to collate a list of users from all the Projects and Teams for audit purposes.
To get all team names I was using https://hostname:9443/ccm/rpt/repository/foundation?fields=foundation/teamArea/name. I noticed some teams were missing, but when I ran another query on the specific Team name which was missing I got positive results back , and could even get a list of members for it. https://host:9443/ccm/rpt/repository/foundation?fields=foundation/teamArea[@name='Missing Team_Area']/name Am I doing something wrong or is this a bug? If it is a bug is there a workaround please. Thanks For what its worth - the following command is what I was using to get related ProjectArea, TeamArea and users which is what I need. https://host:9443/ccm/rpt/repository/foundation?fields=foundation/teamArea/(name|projectArea/name/name|parentTeamArea/name/name|teamMembers/name |
One answer
|
Thanks for your reply Donald. It turns out the data returned is limited to 100 records. Some colleagues came across the same problem. The href which is returned in the browser with the data includes the following suffix "&size=100&pos=100" which provides a reference to the next set of data available for the query. If I append that to the end of the url it gives me the next 100 records. I was advised against just increasing the size as they had experienced problems with this - perhaps it is overridden by the server.
It explains why data was missing anyway. |
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.
Comments
I really doubt that the field selection can affect the result set. If you compare the missing team area and the normal ones, do you notice any difference? Also, does "?fields=foundation/teamArea/*" return all the team areas?