Hot Fix Readme (Adapt) - Business Intelligence

CHF17
ADAPT00672037
Description:
Patch ID: 39,599,310
When users drill down on a subreport in the .NET Web Form viewer, the following error message may appear: "Invalid length for
a Base-64 char array."
This problem happens when the name of the subreport contains a greater-than symbol (>).
New Behavior:
This problem is resolved.
ADAPT00673516
Description:
Patch ID: 39,592,786
If the RAS Java SDK is used to change a table's datasource to an XML result set, the database tables may be automatically
removed from the report.
The cause of the problem is that the request to change the datasource location will internally execute a verify database
procedure against the current datasource location. The verify database procedure is started before the table is modified to use
the new datasource location. If the datasource is found, the program may remove the tables from the report if no match is found
for the table. If the datasource cannot be found, the report will display the report with data from the XML files.
New Behavior:
This problem is resolved.
To solve the problem, an option has been added to bypass the internal execution of a verify database procedure. In general, this
option will not be required because the table stripping will only occur when the same table is not matched. However, this option
is useful when the datasource exists with the same name but does not have matching tables.
To use this option, a tag set named "VerifyDatabaseOnSetDataSource" has to be added to the RAS configuration file:
clientSDKOptions.xml. For more information about clientSDKOptions.xml, see the "Setting up your RAS environment" section
of the RAS SDK Developer Guide.
To enable this option, the tag set false must be
manually added to the CrystalReports.ClientSDKOptions section in clientSDKOptions.xml. A value of "false" will bypass the
internal verify-database call.
For example, the following code will bypass the verify database call:
LOCALHOST
TCPIP
false