Getting an error that oscl_query_api is unable to parse query when I use the -q flag for anything except dcterms:identifier #78
Replies: 4 comments
-
Is this for DOORS Next? If not, which app? What version? Are you running oslcquery on Windows or Linux? |
Beta Was this translation helpful? Give feedback.
-
The OS-specific challenge is the quoting correctly on the command line. I'm using Windows. For Windows: To query a value use the attribute name surrounded by ' then = or in and then on the RHS the string/number literal or the enumeration value name in ' For example -q "'Risk'='High'" I don't know how that works on Linux where commonly ' is used to quote for the shell. Let's hope you're on Windows. |
Beta Was this translation helpful? Give feedback.
-
Or if you're trying to find artifacts of type Risk in DOORS Next then use -q "oslc:instanceShape='Risk'" If you're doing this on EWM then it's probably a bit different like -q "rtc_cm:type=Risk" |
Beta Was this translation helpful? Give feedback.
-
To find items modified since a date (similar for created) use a query like Yes you have to use a full time like that. Yes it has to use UTC (Z) time. You'll have to quote this appropriately for your OS. |
Beta Was this translation helpful? Give feedback.
-
I am trying to find all 'Risk' items in a project. In a select * with -q on a known risk item I am able to successfully pull data and the output shows the column dcterms:Type with a value of "Risk". However when I am using the -q flag with 'dcterms:Type="Risk"' I get an error processing a complex query exception from Oslcqueryapi.py that there is an error with parsing my complex query. I have tried using rtc_cm as a prefix, and about every permutation of quotation marks possible. Do you know what may be going on so I am able to successfully query using the -q flag? It also is not working for me when I try to search using a -q flag for min date. Thanks
Beta Was this translation helpful? Give feedback.
All reactions