It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×3,951
×332
×44

question asked: May 30 '13, 5:42 a.m.
question was seen: 5,842 times
last updated: Aug 13 '14, 10:35 a.m.

Related questions

How to use "Views" artifact type in the reporting interface of RRC

0
Derek Moyle (1●5●4) | asked May 30 '13, 5:42 a.m.
The RRDG template supplied for "printing" modules in RRC uses the artifact type of views. I am unable to find any documentation on how to use this.

I can get the schema for it via https://<servername>:<portno>/rm/publish/views?metadata=schema but I can not get any data out of it. What parameter(s) does the views artifact take? Everything I have tried (via a web browser) other than requesting the schema just returns:
CRRRS6536E No view was found to in the request (More info found at entry [829e2f86e6b3544f] in the RM application server log)

Any guidance or documentation on using the views artifact type would be appreciated.
Comments
Fabian Lomeli commented Jun 04 '13, 5:51 p.m.
JAZZ DEVELOPER

Something might be occurring in your server.  You should see the rm.log and look for the 829e2f86e6b3544f entry for further details about the problem.  However you can find out more information about Reportable Rest API here:
RRCReportable Rest API

Fabian Lomeli commented Jun 04 '13, 5:52 p.m.
JAZZ DEVELOPER

Sorry, the more specific link is Artifact types on 3.0.1

3 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Thomas Wiman (31●2●3) | answered Jan 30 '14, 6:27 a.m.

Any news on this issue? I have exactly the same problem.

It is possible to get the views schema but not the data.

I am running RRC 4.0.5

0
permanent link
Mike Jaworski (1.4k●6) | answered Jan 30 '14, 8:15 a.m.
JAZZ DEVELOPER
Hi all,

If you follow the link from Fabian's comment above (RRCReportableRestAPI), it looks like "views" is not a supported artifact format that you can use through the Reporting REST API. If you are trying to report on specific artifacts from a view, you should probably use one of the following commands:

https://server:port/rm/publish/[artifact_format]?viewURI=id1&projectURI=id2  (If you know the URI of the view)
ex) https://server:port/rm/publish/resources?viewURI=_c1cm0L3VEeCPFbe791FOoQ&projectURI=_bBIqQqvyEeCwWN-gBxjnGw

https://server:port/rm/publish/[artifact_format]?viewName=name1&projectURI=id2 (If you know the name of the view, but not the URI)
ex) https://server:port/rm/publish/resources?viewName=Requirements&projectURI=_bBIqQqvyEeCwWN-gBxjnGw

Hope this is what you are looking for!
Mike Jaworski
0
permanent link
Nate Decker (378●1●47●61) | answered Jun 10 '14, 6:06 p.m.
edited Aug 13 '14, 10:35 a.m.

I think the "views" is a property of Modules which is different from the "view" artifact type in the broader context of the project area.

We are finding that it is necessary to use the undocumented "views" interface because it is much faster than trying to iterate through the module and request data on each artifact within it. It seems like the "views" url requires a cached copy of a view that has been loaded within a module. We were able to get the URI from the logs on the server, but the URL seems to no longer be valid after a server restart.

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.