Importing customAttributes with RQMExcelImporter 3.0.1
What notation should I use to import data from Excel into a customAttribute?
Is it something similar to the import of categories? testcase.category term="Function".value=H A GET whith the RQMUrlUtility gives this: <customAttributes> <customAttribute> <identifier>Kravflode</identifier> <name>Kravflode</name> <value>Test av meddelande</value> </customAttribute> </customAttributes> Another issue is that if I use special characters (Swedish, ) in the names of categories when, defining them in RQM 3.0.1, the RQMExcelImporter puts another character in their place in the resulting XML. Even if I replace the character with the original character so the names matches the RQMExcelImporter will not import it when I do a Export to repository. |
9 answers
The RQM Excel/Word Importer is based on the RQM Reportable REST API (https://jazz.net/wiki/bin/view/Main/RqmApi), which defines the resource/property support (https://jazz.net/wiki/bin/view/Main/RqmApi#Detailed_Schema_Documentation) and XML notation (https://jazz.net/wiki/bin/view/Main/RqmApi#ScenarioCreateTip). For more information on the customAttributes property, see (RQM 3.0.1):
https://jazz.net/projects/rational-quality-manager/api-doc-3.0/api-files/schemas/qm_xsd/elements/customAttributes.html When using the RQM Reportable REST API (https://jazz.net/wiki/bin/view/Main/RqmApi), special characters ( ) in URL must be XML encoded (see http://en.wikipedia.org/wiki/Percent-encoding). For example: %C3%A5+%C3%A4+%C3%B6 If you are familiar with Java, you can use java.net.URLEncoder.encode(String). |
Did the issue of importing the customAttributes ever get resolved?
i am looking to import data into the Test Plan level custom in RQM 3.0.1 |
|
There was no issue to resolve.
|
|
"What notation should I use to import data from Excel into a customAttribute?
Is it something similar to the import of categories? testcase.category term="Function".value=H " This is the question i am referring to. Using examples as testplan.attribute name="blah".value=D testplan.customattribute name="blah".value=D etc. i could not get it to work. |
|
I did not get the import of custom attributes to work with RQMExcelImporter 3.0.1. An example would be nice.
Also when I use percent-encoding in the configuration file to populate a category named 'Kravflde' it creates a new category named 'Kravfl%C3%B6' |
|
Unfortunately, the RQM Excel/Word Importer does not (yet) support importing custom attributes (https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/52633), although the RQM Reprotable REST API does support PUTing/POSTing custom attributes. For example:
<qm> <qm> <qm>CustomAttributeID</qm> <qm>CustomAttributeName</qm> <qm>CustomAttributeValue</qm> <qm>CustomAttributeDescription</qm> </qm> </qm> Values for type are: SMALL_STRING MEDIUM_STRING INTEGER TIMESTAMP |
I did not get the import of custom attributes to work with RQMExcelImporter 3.0.1. An example would be nice. See https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/52633. Also when I use percent-encoding in the configuration file to populate a category named 'Kravflde' it creates a new category named 'Kravfl%C3%B6' What exactly is the symptom when you do not encode the value? |
|
The work item at:
https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=55556 describes a way to get the excel importer to uplaod custom attributes as: " execution.executionresult.customattribute1=TIMESTAMP:0:TR_attribute_3 execution.executionresult.customattribute2=SMALL_STRING:1:TR_attribute_1 " do you think we could implement this code into the testplan level as: testplan.customattribute1=TIMESTAMP:1:TR_attribute_3=A testplan.customattribute2=SMALL_STRING:1:TR_attribute_1=B in theory this would populate the firs tattribute of the test plan (in the case is a date named TR_attribute_3) from cell A. |
|
Please see/comment in https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/57229.
|
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.