I know it's possible to export styles, but the sharing of styles between reports could use some improvement. My developers regularly create templates, which hold the report settings, page layout, etc., and then inherit from those template. For simplicity, style settings are stored in the report rather than external style sheets. If you want to create a different template, but use the same styles (for example to create a landscape version) you have to manually recreate the styles in the new report, or try copying the styles from the original designer file to the new one (which often renders the new report unusable in our experience).
I know we can export the styles and reference an external style sheet in the new report, but in practice that complicates code management and deployment so we generally avoid it. I think the ideal solution would be to provide a *true* import function; the ability to import styles, either from an external XML file or directly from another report, so that the styles are stored within the report definition directly and no external XML file is required at runtime.
I know we can export the styles and reference an external style sheet in the new report, but in practice that complicates code management and deployment so we generally avoid it. I think the ideal solution would be to provide a *true* import function; the ability to import styles, either from an external XML file or directly from another report, so that the styles are stored within the report definition directly and no external XML file is required at runtime.