Why is work item Reportable REST API returning a different String Extensions field order? How to control String Extensions field order or return a unique XML TAG name?
I have encountered a critical issue with our Production implementation of RTC. I'm getting a different order of XML results between our RTC test and RTC production areas.
URL:
https://server:port/ccm/rpt/repository/workitem?fields=workitem/workItem[projectArea/name='MiCSES Change and Configuration Management' and (id=293)]/(children/stringExtensions[key='micsesSmStrCiName' or key='micsesSmStrCiVersion']/value)
Output from Test RTC (CI Name is listed before CI Version):
Output from Production RTC (CI Version is listed before CI Name):
Background:
I created and defined these 2 custom fields in Test RTC and Prod RTC in the same order.
We are using the XML to load data into a database table.
Questions:
1) Why is the returned XML order different between Test RTC and Prod RTC?
2) Is there a way to control the returned XML order of these fields? How?
3) Alternatively, is there a way to request/specify unique XML tags returned for each of the fields?
- In order to load the correct data into the correct column, we need a unique field ID. Right now all String Extensions are tagged with "<stringExtensions><value>" even when the values are coming from different custom fields.
2 answers
https://server:port/ccm/rpt/repository/workitem?fields=workitem/workItem[projectArea/name='MiCSES Change and Configuration Management' and (id=293)]/(children/stringExtensions[key='micsesSmStrCiName' or key='micsesSmStrCiVersion']/(key|value))
Comments
Michael Taylor
Sep 17 '13, 12:10 p.m.Michael Taylor
Sep 17 '13, 1:02 p.m.