Is it possible to change the format of a Jaspersoft report when the operator is requesting an export?
My customer wants the report heading removed if he is exporting the report to a XLSX file.
I thought of several options: clearing the text field that contains the heading; deleting the page header section, etc but they all require detecting that an export is being done. Are there any builtin functions that do that?
Or is there a way to specify that one format is used for display and another format is used for export?
I received an answer from the Jaspersoft community
To remove header on export:
<property name="net.sf.jasperreports.export.xlsx.exclude.origin.band.1" value="pageHeader"/>
To remove footer on export:
<property name="net.sf.jasperreports.export.xlsx.exclude.origin.band.2" value="pageFooter"/>
Related
I used this line in wxl file to add custom message but still not able to align the version number properly
<String Id="WelcomeDlgDescription" Overridable="yes">The Setup Wizard will install [ProductName] on your computer. Click Next to continue or Cancel to exit the Setup Wizard.
{\WixUI_Font_Title}Version - [ProductVersion]</String>
I want the results to be like this
Also, I am not able to change the fonts.
Updated
I am able to achieve this. Version left hanging in the middle and not going at the end,
Limitation: It looks like you can only have one style per string. I am not sure, but it says in the documentation that you have to refer to the style at the beginning of the string:
<TextStyle Id="Test" FaceName="Arial" Blue="255" Size="12" Strike="yes" />
<..>
<String Id="WelcomeDlgDescription">{\Test}Version - [ProductVersion]</String>
Adding Controls and Text
ICE31 - validation suite checking Strings and fields (see Examples)
Customizing WiX Dialogs: You might need to change the whole dialog to add two fields so you can put the version number in its own
text box featuring its own style. Doing so is a little involved, and I have a description of
it here: Customizing WiX Dialogs. Please have a quick read. It also describes how to change font color and style.
Update: Nice little sample for how you can insert a custom dialog: Wix UpgradeVersion.
I am using WIX Toolset to create MSI Application and I want to provide my own License file to display during the license Agreement on License Agreement Dialog.
I created a new document in word-pad and saved it with .rtf extension. Whatever the content of document wix is not getting build and the error which comes is error LGHT0311.
C:\agent\_work\8\s\src\ext\UIExtension\wixlib\LicenseAgreementDlg.wxs(27,0): error LGHT0311: A string was provided with characters that are not available in the specified database code page '1252'. Either change these characters to ones that exist in the database's code page, or update the database's code page by modifying one of the following attributes: Product/#Codepage, Module/#Codepage, Patch/#Codepage, PatchCreation/#Codepage, or WixLocalization/#Codepage.
Note:- LicenseAgreementDlg.wxs(27,0) contains this line <Text SourceFile="!(wix.WixUILicenseRtf=$(var.licenseRtf))" />
I have tried adding Codepage value as 1252 in Product tag and SummaryCodepage in Package Tag. I have tried even by putting only one character in License file but still getting same error.
Please help me solving this issue?
You need to create your license with WordPad and save it with *.rtf extension.
I was creating the license with Microsoft Office Word, and then saving with *.rtf extension, which was giving error like above.
How can I link from a Sphinx document into a CHM file?
It seems that I could link from one chm file into another using a syntax like
<a href="ms-its:path+filename.chm::/pagename.htm">
Is it possible to transfer this into Sphinx commands?
You know, opening a topic compiled into a CHM is possible with Microsoft Internet Explorer only (!) by adding following code in a HTML file:
<p>Sample of CHM link to a topic in a compiled help file that is stored on a local computer</p>
<!-- To link to a topic in a compiled help file that is stored on a local computer, create a link using the following syntax: -->
Link to Garden topic here
I think, the reStructuredText parser cannot transfer these special kind of link from the source (reST).
But you can use the Replacement Text like shown below. Please note, the backslash is used twice:
================
Replacement Text
================
I recommend you try |HTMLHelp|_ and continue compiling help in CHM file format.
.. |HTMLHelp| replace:: CHM, *the* best help format around
.. _HTMLHelp: ms-its:D:\\UserData-Sphinx\\CHM-example.chm::/garden/garden.htm
The "replace" directive is used to indicate replacement text for a substitution reference. It may be used within substitution definitions only.
The resulting HTML file view:
The compiled help CHM:
The topic garden.htm is shown in the Help Viewer's topic pane after the link iswas clicked:
You may download the above used CHM-example.chm file from my HTMLHelp (HH) info site see download section or download CHM.
Please note, to open this CHM file right-click the saved file, click Properties, and then click Unblock.
I'm trying to upgrade from Magento Community to Magento Enterprise. I've got each installed seperately. I did a direct export of product from my Community installation and have attempted to directly import this to Enterprise.
Initially, the error I was received was
'csv' file extension is not supported
I did the following according to a reply on a forum post from someone with a similar problem:
Disable the Magento Compiler under System > Tools > Compilation
However, the next Validation Error I encountered was this:
Column names: "_root_category", "_group_price_website", "_group_price_customer_group", "_group_price_price", "_media_attribute_id", "_media_image", "_media_lable", "_media_position", "_media_is_disabled" are invalid
I've done zero editing to the product CSV Magento provided me. I duplicated it, opened up the file and have found zero problems and zero duplicated columns.
I'm at a loss as to what to do next, any suggestions?
Sample CSV
Link: - Google Docs Preview
Link - Google Drive Download
Open in a text editor and save as UTF-8 encoding
Make sure you are using Import/Export > Import rather than the deprecated Dataflow method of import
In development of a text editor application, I came across a need to test an .ODM format (OpenDocument Master Document) support. I tried searching OpenOffice documentation for samples, but failed to find any.
Please suggest where to find such samples.
You can make them with OpenOffice.org Writer.
I did it once just to see how it worked.
OK, I am using the ODF 1.2 Specification Part 3 because it is not too large but has several chapters.
So I opened OpenDocument-v1.2-cs01-part3.odt (actually using LibreOffice 3.3.2 but OpenOffice.org 3.3.0 and earlier work the same way).
On the menu bar select File | Send > Create Master Document
This will give you a Name and Path of Master Document dialog, with Save as type set to ODF Master Document (*.odm).
I navigated the Save dialog to the folder where I wanted to save the Master and its parts. I then specified MasterDocDemo. There's a Template setting pull-down which defaults to Outline Level 1. I left that alone and clicked "Save." I ended up with an 8-part document:
MasterDocDemo.odm
MasterDocDemo1.odt
MasterDocDemo2.odt
...
MasterDocDemo7.odt
Do that yourself with something that has chapters or something with headings at Outline Level 1 and then explore.
Opendocument format 1.1 specification on schemacentral
You can find all type of open document format specification provided by OASIS here. (including v1.1, v1.2)
LibreOffice and OOo supports this format. To create ODF master doc you can export odt files to odm from Lo or OOo.