Hot Fix Readme (Adapt) - Business Intelligence
Hot Fix Readme (Adapt) - Business Intelligence
Hot Fix Readme (Adapt) - Business Intelligence
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
CHF14<br />
ADAPT00634999<br />
Description:<br />
Patch ID: 39,218,616<br />
When reporting data changes, the Navigation Pane fails to display new information when a Desktop <strong>Intelligence</strong> report is<br />
refreshed in JAVA InfoView.<br />
New Behavior:<br />
This problem is resolved.<br />
ADAPT00635857<br />
Description:<br />
Patch ID: 39,208,685<br />
Desktop <strong>Intelligence</strong> reports are slow when handling complex Universes even before the reports are refreshed against a<br />
database.<br />
New Behavior:<br />
This problem is resolved.<br />
ADAPT00636106<br />
Description:<br />
Patch ID: 39,217,867<br />
When a user imports reports from Crystal Enterprise 9 to <strong>Business</strong>Objects XI Release 2 using the Import Wizard, if the user<br />
logs onto .NET InfoView or Java Infoview and expands the static parameters on an imported Crystal Enterprise 9 report, the<br />
following error message appears: “The database logon information for this report is either incomplete or incorrect.”<br />
New Behavior:<br />
This problem is resolved.<br />
ADAPT00636442<br />
Description:<br />
Patch ID: 39,225,956<br />
Options for the Drill feature fail to work properly after cells have been merged.<br />
New Behavior:<br />
This problem is resolved.<br />
ADAPT00636524<br />
Description:<br />
Patch ID: 39,222,945<br />
The incorrect number of members or incorrect order of members is displayed when Crystal Analysis version 10 reports with<br />
reordered members are opened using OLAP <strong>Intelligence</strong> XI Release 2.<br />
The cause of the problem is that the calculations fail to be added in the proper order because the calculations fail to be added<br />
to Multi Dimensional Expressions according to their order in the XML file. In addition, some members fail to appear at all<br />
because they are saved in the XML file in such a way that white space is generated around the member names and thus cannot<br />
be matched using string comparison methods.<br />
New Behavior:<br />
This problem is resolved.