Article ID: K00000516
Last Updated: April 20, 2016
Summary
This article describes the changes included in Report Commander 2.2, released on April 20, 2016.
Note: This is a free update for all adTempus 2 users. No license update is required.
Upgrading
If you are upgrading from a previous 2.x version, run the installer to upgrade your existing installation in place. It is not possible to install this release side-by-side with an earlier 2.x release.
If you are upgrading from version 1.x, see the download page and the user guide for installation and upgrade information.
Obtaining the Update
See the download page to download the latest version of Report Commander. The setup program will update your installation.
Changes in This Update
This release corrects issues discovered since version 2.1. See article K00000502 for changes in version 2.1.
The following changes are included in this update:
Command Line Builder |
| Command Line Builder crashes when you click the Text Edit button for e-mail sender | CR00007123 Defect | |
Command Line Builder does not generate some options properly | CR00007125 Defect | When some true/false options are not checked in the Command Line Builder, the generated command line does not include settings for the options. When the command is run, the default setting of "true" is used instead of the desired "false" setting. Affected options:
- flattenhtml
- exportimages
- worksheetfunctions
- maintainalignment
- simplifyheaders
|
|
General |
| New syntax for command-line override of database connections | CR00007151 Enhancement | When you specify credentials for or override a database connection using the "-login" option on the command line, Report Commander now supports a new syntax that better handles complex override scenarios.
The Command Line Builder will now generate command lines using the new syntax. The old syntax will continue to work.
The new syntax is as follows, with all sections optional:
-login:{server:new server}{database:new database}{schema:new schema}{userid:user ID}{password:unencrypted password}{encryptedpassword:encrypted password}
Note: The password or encryptedpassword section must come last.
For example, to set just the user ID and password:
-login:{userid:albert}{password:P@ssw0rd}
To use an encrypted password generated by Report Commander:
-login:{userid:albert}{encryptedpassword:5pkVfiMJHp2MsPoZUsPKc2zSRD7O94Jx}
To override the database name and set user ID and password:
-login:{database:proddb}{userid:albert}{password:P@ssw0rd}
See the user guide for more details. |
Added Parameters panel and Export command to Preview window | CR00007165 Enhancement | When you preview a report in Report Commander, it is now possible to export directly from the Preview window.
A button has been added to toggle display of the parameters panel. Parameter values entered here only affect the preview and are not saved for use in other Report Commander processing.
|
Report Commander uses wrong settings for Excel XLSX format | CR00007124 Defect | When using the Excel XLSX export format, Report Commander should be showing/using the same options as are shown for Excel Data Only format. Instead it shows the options used for Excel XLS (92-2003) format. As a result, settings are not passed correctly to the Crystal Reports runtime, and exports may not be formatted as expected.
This problem was corrected. |
Wrong variable values used when project contains multiple reports, outputs, or tasks | CR00007129 Defect | When a project contains multiple reports, outputs groups, outputs, or tasks, variable values from one item might get reused when processing a later item. For example, if you have a project with two reports, and each report has a file output configured to use file name "${Report.Name}.pdf", both exports may use the name from the first report. |
When project contains multiple reports, predefined variables from first report appear in variable selector for all reports | CR00007130 Defect | |
"Read settings from command line" fails to process command line properly in some cases | CR00007144 Defect | The "Read settings from command line" feature in the Project Editor and Command Line Builder fails in some cases where the command line contains spaces contained in quotes, causing it to interpret the report file name incorrectly and report that it cannot be found. |
Option to print report is missing from Preview window | CR00007145 Defect | Previous versions of Report Commander included a Print button within the report preview window. The option was omitted from Report Commander 2 but has now been restored. |
Add option to use RAS printing engine | CR00007149 Defect | A new option was added to use the RAS printing engine instead of the default print engine. This engine is only needed when you are affected by the problem described in article K00000508.
To use this option, add the following option to the Report Commander command line:
-reportengine:ras
Alternatively, select the "RAS" setting for Report Engine in the Print Output properties.For more information see Knowledge Base article K00000508. |
Connection may not be overridden if report uses more than one Command as a data source | CR00007150 Defect | If a report uses more than one database Command as a data source and you override the database connection, the override may only get applied to the first command. |
Report Commander does not generate HTML-format e-mail message when HTML message specified on command line | CR00007152 Defect | If you use the "-emtext" command-line option to specify the text of the e-mail message and your text includes HTML tags, Report Commander still created the message as a plain-text message, resulting in the HTML tags being included in the message as plain text. This was fixed to detect HTML tags and use HTML format. |
Invalid parameter value error when optional parameter omitted | CR00007164 Defect | When a report has an optional parameters and you process the report using the Command Runner (adcrutil) without specifying a value for that parameter, processing fails with error "The types of the parameter field and parameter field current values are not compatible." For more information see Knowledge Base article K00000513. |
|
Project Editor |
| Add ability to duplicate reports, output groups, outputs, and tasks in the Project Editor | CR00007128 Enhancement | You can now duplicate a report, output group, output, or task in the Project Editor. Right-click the item in the editor tree and select the "Duplicate..." command. |
|