nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deployed BIRT reports has no CSS

aleksandar.d

Hi everyone,
 
So I've made a report using a theme from my company's library. Library is included with report. I was asked to send the .rptdesign file to be deployed in our app. (I have no information how app works)
 
When they open the file in app, no css is there and report is just plain text. This isn't first report that is using a library resource that is being deployed, but it's the first one in some time, so I can't ask anyone what to do to fix it.
 
Only difference that I've noticed between mine and a report with working css, is that it doesn't have any theme applied but instead has all the styles from the theme listed in style part of report outline.
 
Is there anyway to add styles from a theme in library, to styles in report? I can't seem to find it, there is only option to apply theme and it works perfectly but only on my PC.
 
Thanks in advance

Find more posts tagged with

Comments

JFreeman

Was the report library that is used in the report for the themes published with the report?
 
My guess is that your app server cannot find the report library that contains the theme(s) for the report.

aleksandar.d

Yeah, that is my guess too but I have no knowledge how the app works, I made it work by copying the styles from the library to my report's styles but that's not really a great solution.
 
What do you mean by is it published with library? It's listed in outline view in library folder, but is there a way to actually link the library with report?

JFreeman

You are referring to using a theme from an .rptlibrary file correct?
 
The .rptlibrary is a separate library file that is referenced through a relative path from the report design but it is not actually included into the report design.That library file needs to also be deployed to the app so that it can be found in that relative path location referenced in the report design.