It's all about the answers!

Ask a question

Execute queries created in the RTC Query Editor via Reportable REST API

Michael Taylor (8865764) | asked Jun 24 '13, 3:49 p.m.
edited Nov 19 '20, 6:49 a.m. by Ralph Schoon (63.2k33646)

Can the Reportable REST API (https://<server>:<port>/ccm/rpt/repository/workitem?fields=workitem/workItem/...) be used somehow to run a query that was created in the RTC Query Editor?

   I see that this can be done using OSLC:  I want to know if this can be done using the Reportable REST API. 

Reference old question:


One answer

permanent link
Stephane Leroy (1.4k149) | answered Jun 25 '13, 2:10 p.m.
Hi Michael,

contrarily to what I stated previously in  you could not execute a query using OSLC. 

At least not using OSLC v2.0 (i.e. with the header OSLC-Core-Version set to the 2.0 value in your GET header).
The alternate way I'm aware of is to build a query (directly in the URL - note that these are not the predefined queries you created before in the UI or the Eclipse client)  by filtering on specific attributes, etc on top of base query URL. For a reference on this: check

My initial answer was based on the information returned using OSLC-Core-Version 1.0
Indeed additional data were returned. For example (this is coming from a try I had today on my 4.0.3 CLM server):
<oslc_cm:Collection xmlns:oslc_cm="" oslc_cm:next="https://localhost:9443/ccm/oslc/queries?oslc_cm.pageSize=50&amp;_resultToken=_Kk8-Ut29EeKJf8PdPIFoYQ&amp;_startIndex=50" oslc_cm:totalCount="121" xmlns:dc="" xmlns:rdf="" xmlns:rtc_cm=""><rtc_cm:Query rdf:resource="https://localhost:9443/ccm/resource/itemOid/"><dc:identifier></dc:identifier><dc:title>Retrospectives</dc:title><rtc_cm:projectArea rdf:resource="https://localhost:9443/ccm/oslc/projectareas/_4xR-UTQIEeKrSIP2Razv7w"/><dc:description>Find all Retrospectives.</dc:description><rtc_cm:results oslc_cm:collref="https://localhost:9443/ccm/oslc/queries/_5p8rsDQIEeKrSIP2Razv7w/rtc_cm:results"/><dc:creator rdf:resource="https://localhost:9443/jts/users/sleroy"/><dc:modified>2012-11-21T18:26:01.026Z</dc:modified><rtc_cm:modifiedBy rdf:resource="https://localhost:9443/jts/users/sleroy"/></rtc_cm:Query>....
Additional content exhibits URLs (like the https://localhost:9443/ccm/oslc/queries/_5p8rsDQIEeKrSIP2Razv7w/rtc_cm:results) that typically returned the associated work-items.

For now, I don't believe this would be a recommended practice.
Also, you shall keep in mind that loading Jazz server with too much REST calls could introduce performance problems (this was already pinpointed to you by other Jazz developers).
So  I'd strongly discourage you to investigate towards this (old) solution.

Hope this clarified things and sorry for the convenience if my guidance was (temporarily) misleading.
Note: I shall make sure the wiki topic also states things more precisely.


Erwin Kunz commented Apr 23 '14, 6:48 a.m.

Hi Stéphane
Is there a way to have the query schema as datasource in RPE
I tried like all other datasources as follow:


Stephane Leroy commented Apr 23 '14, 12:01 p.m.

Hi Erwin,
I'm unsure about what you're trying to do but.... have you checked this DevWorks Q&A already ? Any helpful ?

Erwin Kunz commented Apr 24 '14, 8:22 a.m.

Salut Stéphane

My goal is to create a RRDG report in RTC where the user can select a query which the report will use to query the work items.

RTC/RRC/RQM do return the schema when using ?metadata=schema what is needed in RPE. The other possibility is to have a XSD file describing the data schema.

Stephane Leroy commented Apr 24 '14, 8:58 a.m.

it's my understanding the devWorks forum question I mentioned above could help wrt.  "the other possibility" (XSD file). Correct ?

Erwin Kunz commented Apr 24 '14, 10:29 a.m.


Any idea where I can get the XSD description of ../ccm/oslc/queries


Stephane Leroy commented Apr 24 '14, 10:34 a.m.

In this resource, Dragos points to some external tooling (XML->XSD). I've not checked it myself  but this may worths a try...

showing 5 of 6 show 1 more comments

Your answer

Register or to post 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.