Report Builder filtering xhtml tags of primary text
Hi there,
I am having trouble exporting primary text using Report Builder. It seems that the report builder (even when retrieved through REST) somehow filters the primary text. For example when an artefacts xhtml content uses tables (<table>...</table>) all the related tags are removed from the output even though the original xhtml content can be found in the data warehouse table (RITRS.REQUIREMENT.LPRIMARY_TEXT). Is there any possibility of switching this filtering off?
One answer
Dear Bjorn,
IBM Engineering Report Builder is displaying primary text (content) as a plain text and is removing all html tags from the text and table is only one them that you mentioned.
As it was designed the IBM Engineering Report Builder is not proving support for Rich Text and in such a case IBM Engineering Publishing should be used.
Comments
Hi Bartosz,
thanks for the clarification. I was hoping it would be possible to just get the value as it can be found in the database. The problem with using the REST based approach with IBM Engineering Publishing is that it is taking very long for huge numbers of artefacts, i.e. I need to do one REST call per artefact in order to retrieve "dataSource/artifact/content/text/richTextBody/div/_value".
This is so timely. One of the IBM Champions, Peter Morgenthaler, and I were only trying to find this out last week.
I can totally understand filtering out most of the rich text elements when you're displaying in the UI, or when you're exporting to Excel, but it would be really useful if the PUB export set some kind of parameter in the URL and the data source feed going into the PUB template from a Report Builder report had the full XHTML, because PUB can handle it
1 vote
Hi Davyd,
that is exactly what I was hoping for as well. It would make life much easier in many cases, i.e. cutting down run times of some PUB reports from 20+ hours to 20 minutes.
I was also surprised that there seems to be no way around the XHTML filtering using advanced queries.
So Peter and I played with this today. We found the lqe end point for raw queries using the low level query editor, and were able to create a source that let us pull primary text. If it works then we see the potential for speed increases like you mention
1 vote
That's great to hear. Having an endpoint which can receive raw queries from PUB sounds like a dream come true. In some settings, I would really like to be able to somehow parameterise report builder queries. Currently, I have to copy whole reports and just change small things in the queries and then choose the appropriate rs report from PUB.
By low level query editor do you mean the "advanced section" of the "Format results tab" in report builder?
The Query section in the LQE application itself
showing 5 of 6
show 1 more comments