RPE RM Deployed Reports with multiple inherited data sources of the same type
I have created a traceability reports starting from a module
My first data source is "modules"
Next, I have a data source of "_text" to pull in the details about the module requirements which cannot be pulled in from the module context binding. (attribute and rte version of primary text etc)
Now...I want to get the traced components and pull in similar information. I'm able to do this by making a data source "_resources", but it does not appear give me all the primary text
According to this white paper, deployed reports must follow strict naming conventions. "modules" "_text" "_resources" etc.
How do I get a second text data source onto the report and still make it deployable?
3 answers
You may try appending ptext=true to the request URL so as to get primary text.
To get second text data source, you can use the name of any other artifact type format. It need not be "text" or "_text", though you are using the schema of text artifact type. Another option is to reuse / reconfigure the same "text" data source.
Comments
Celia
What versions of RPE and RM are you using?
Your RPE reference is using: "RPE 1.2.1.1 with DNG 4.0.6"
The latest RM/DNG is 6.0.x and newest RPE is 2.1.1
so I expect many differences from significant progress.
Comments
Okay! I finally found the issue -using the rmReporting.logs. Lessons Learned: Be careful about re-use. Sometimes there may be corruption which could be carried over to a new report
Originally, the report had two passed thru a selected module. First pass printed the module. Second pass was a trace matrix.
For production, we split the report into 2 parts. First part was deployed successfully to production. For the trace matrix, I copied a container form the second half of the report into a new report.
I ran both reports on production and looked at the logs. The URL from the first report was fine. The URL from the recycled 2nd half of the report was different and not compatible with the data source schema. I made a new module data source and removed the old one. Success!