Erik Mats (
105●8●25)
| answered Feb 29 '16, 5:17 p.m.
I think I have a way to identify the data you are requesting, using a REST API call, the same way that the ETL jobs fetch data.
1. Try this REST API call:
https://SERVER/ccm/rpt/repository/foundation?fields=foundation/teamArea/(itemId|qualifiedName|teamMembers/(itemId|name))&size=100000
The output will be:
- For each team area (by itemId and qualified name)
-- list all users (by itemId and name)
2. Save the output XML to a file "UserData.xml"
3. The top of the XML output will be a link to the "next" page which I expect will be empty. If not, follow that link and concatenate the result to "UserData.xml". Repeat if needed.
4. Then run this on a Linux or Cygwin command line:
cat UserData.xml | sed 's/teamMembers><itemId>/@/g' | tr '@' '\n' | cut -d '<' -f 1 | sort | uniq -c | sort
The output will be number of team areas for each user itemId. Example:
1 _CqtAAGaLEeSzX8ALDnR3YA
3 _NCdyQHYnEeSnLYxGo5NAEw
5 _19zx0HCqEeSSpfO5JdNebQ
6 _2ArfoXCqEeSSpfO5JdNebQ
5. You can search the file UserData.xml for ItemIds to match them to user, OR open any user in jts/admin and then replace the itemId at the end of the URL with one found this way, to map the itemId to a user identity.
Ralph Schoon selected this answer as the correct answer