I'm using version 11.52, and I am tasked with copying a series of graphs, or AnalysisItems. I have not found any way to retrieve graph data directly from the AnalysisItem, so my approach is to extract the filter in these AnalysisItems, and copy them into a working REST-call. This works in most cases, but I am having trouble with chained joins. Here is an example filter from one of the AnalysisItems:
Filter: Test: Project["My Project"]; Cross Filter: <Cross Filter Test Instance-Test Set>Test Set Folder[^Root\My Path\My Project\My Tests^]
I can easily find test instances under the project, by name. It goes like this:
.../test-instances/?query={test.user-18["My Project"]}
of course, this requires that we use the user-18 field for storing project name, which is a logical partision used in my company, within the defined Projects that is a QC entity.
However, if I want to cross filter these found test instances, with instances found only within the test sets within a specific folder, i would have to do something like this:
.../test-instances/?query={test.user-18["My Project"];test-set.test-set-folder.name["^Root\My Path\My Project\My Tests^"]}
however, this gives me an error, stating that "Entity: test-set does not have a field named: test-set-folder.name. Now I knew that, but I hoped that it would understand that the part before the last punctuation mark, was also a relation. It doesn't.
Ive also tried:
.../test-instances/?query={test.user-18["My Project"];test-set[test-set-folder.name["^Root\My Path\My Project\My Tests^"]]}
but nested square brackets doesn't work either.
Lastly I tried a syntax I've seen in the database in "filter-data", and it looked like this:
.../test-instances/?query={test.user-18["My Project"];test-set[x]test-set-folder.name["^Root\My Path\My Project\My Tests^"]}
This is not allowed either.
I feel pretty confident that what I want to achieve is possible, but the documentation is not being very helpful. I reckon if it is possible to set in the filter in an AnalsisItem inside QC's user interface, it should be possible in the REST-API as well.
Can anyone help me with the correct syntax here?