Can RQM or RTC tool validate the records before importing in either of the tools to avoid ETL job to fail?
Can RQM or RTC tool validate the records before importing in either of the tools to avoid ETL job to fail?
If the records imported has invalid date in RQM or RTC then later corrected to the valid date. Then these changes will be saved in work item or test case history and when ETL job tries to insert the history in the REQUEST_HISTORY_TIMESTAMP_EXT table, the ETL job fails as it found an invalid date format in a particular work item. We want the RQM or RTC tool to validate the complete record details before it imports and if it finds an invalid data or date the RQM or RTC import utility should skip this record and proceed with the import of records.
If the records imported has invalid date in RQM or RTC then later corrected to the valid date. Then these changes will be saved in work item or test case history and when ETL job tries to insert the history in the REQUEST_HISTORY_TIMESTAMP_EXT table, the ETL job fails as it found an invalid date format in a particular work item. We want the RQM or RTC tool to validate the complete record details before it imports and if it finds an invalid data or date the RQM or RTC import utility should skip this record and proceed with the import of records.
One answer
Unfortunately, no.
See POST/PUT handlers/lifecycle managers do not check for all required properties. (77973) for required property validation in the RQM Reportable REST API (public API used by the RQM Excel/Word Importer).
Please open a RQM enhancement.
See POST/PUT handlers/lifecycle managers do not check for all required properties. (77973) for required property validation in the RQM Reportable REST API (public API used by the RQM Excel/Word Importer).
Please open a RQM enhancement.
Comments
