Service Pack Readme (Adapt)

CE10WIN_EN_SP4
Separated values
ADAPT00448232
Description:
Patch ID: 37655101
When a report is exported to Character-Separated Values (CSV) and the double-quote character (") is used as a delimiter, the exported copy is
incorrect in fields that contain more than one set of double quotes.
New Behavior:
This problem is resolved.
To solve the problem, double-quote characters are properly padded with an escape character (another double quote) when reports are exported to
CSV.
Known Limitations:
For number/date/time fields, delimiters are removed because characters wrapped in quotes are handled as strings. That is, numbers (1234) are
interpreted as strings (“1234”).
ADAPT00452810
Description:
Patch ID: 37604762
In the Crystal Enterprise Java SDK, the setSameNumberFormat function fails to operate when users schedule a report to character-separated
format. Although no error messages are generated, the function does not perform. The report schedules successfully and its decimal values are
rounded.
For example, a numeric field that displays as 0.0000056 in Crystal Reports will display as 0.01 as a successful instance in Crystal Enterprise.
The cause of the problem is that a property is not being set by the Crystal Enterprise Java SDK, regardless of which boolean is passed to the
function. As a result, the default formatting and rounding is used to create the instance.
New Behavior:
The function now properly sets the property. When setSameNumberFormat is set to true, the successful instances will have the expected number
of decimal places.
Server functionality
ADAPT00175037
Description:
Patch ID: 36622600
An error appears when a report is modified through RAS in ePortfolio. The error reads “Subscript out of range.”
The problem occurs when there are two or more spaces in database field names.
New Behavior:
The problem is resolved.
ADAPT00387704
Description:
Patch ID: 37133258
When users create a report that contains linked parameters, create a custom database logon for the report, and then schedule the report, the
following error message appears when users go to view the report: “The request could not be submitted for background processing.”
New Behavior:
This problem is resolved.