A55005 for 64-bit Enabled Solaris |
SAS Web Report Studio 4.2_M1 |
Issue(s) Addressed: | Introduced: |
37094 | Drilling through to a SASŪ OLAP cube from a SASŪ Web application might fail |
A55001 |
37264 | SASŪ Add-In for Microsoft Office cannot display reports with a general prefilter applied |
A55001 |
37522 | Performance might be slow when viewing a SASŪ Web Report Studio report built from a SAS OLAP cube |
A55001 |
37680 | ERROR: "An error occurred processing the requested group break information" occurs in SASŪ Web Report Studio |
A55002 |
37684 | The SASŪ Add-In for Microsoft Office cannot display reports when SASŪ Web Report Studio is deployed in a clustered environment |
A55002 |
37718 | Some e-mail applications do not indicate the presence of a distributed SASŪ Web Report Studio report |
A55002 |
37818 | Prompt values might be missing for SASŪ Web Report Studio reports opened in the SASŪ Add-In for Microsoft Office |
A55002 |
37834 | ALERT - Certain conditions might contribute to poor performance when you run SASŪ Web Report Studio in Internet Explorer 6 or 7 |
A55002 |
37836 | SASŪ Web Report Studio reports based on a stored process might not honor styles when distributed |
A55002 |
37876 | SASŪ Web Report Studio performance might be slow if a data item is formatted with a user-defined format with many mapping elements |
A55002 |
37965 | SASŪ Web Report Studio reports with linking and "Allow drill-through to detail data" enabled might render slowly |
A55002 |
30734 | Filters might be ignored when viewing detail data |
A55003 |
36329 | Report viewers in SASŪ Information Delivery Portal 4.2 have the ability to navigate to other reports |
A55003 |
36953 | Cascading prompts might not display in SAS® Web Report Studio |
A55003 |
37720 | SASŪ Web Report Studio report fails to open if any data item in the information map does not have a default aggregation specified |
A55003 |
37835 | SASŪ OLAP cubes with an all member that uses a level name might cause client applications to work incorrectly |
A55003 |
37933 | SASŪ Web Report Studio reports that have many conditional highlighting rules might exhibit poor performance |
A55003 |
37964 | Dynamic, multi-selection prompts do not render in SASŪ Web Report Studio if the data item is a formatted numeric category |
A55003 |
38069 | A run-time error might occur after you apply Hot Fix A55001 to the first maintenance release for SASŪ Web Report Studio 4.2 |
A55003 |
38289 | SASŪ Web Report Studio might not correctly export ranges greater than 1000 |
A55003 |
38385 | Newly added banner images appear very small in SASŪ Web Report Studio |
A55003 |
38754 | Sorting on a total column in an OLAP-based SASŪ Web Report Studio report might not work correctly |
A55003 |
38757 | SASŪ Web Report Studio might not be able to retrieve a list of filter values for reports that have an applied identity-driven prefilter |
A55003 |
38768 | ALERT - Group breaks in OLAP-based SASŪ Web Report Studio reports might not work correctly when a section filter is applied |
A55003 |
38813 | Wrong date value might be passed to a linked report in SASŪ Web Report Studio |
A55003 |
38817 | The error "Could not get entry from report repository" occurs when you save a SASŪ Web Report Studio report to a folder named with DBCS characters |
A55003 |
38822 | Linking might not work correctly for SASŪ Web Report Studio reports that display columns over multiple pages |
A55003 |
38978 | An error occurs when you view a synchronized OLAP-based SASŪ Web Report Studio report in the SASŪ Add-In for Microsoft Office |
A55003 |
38981 | An exception occurs when you edit a text object or use conditional highlighting in SASŪ Web Report Studio from a browser with Swedish settings |
A55003 |
38984 | Poor performance occurs when you export detail records from an OLAP-based SASŪ Web Report Studio report |
A55003 |
40020 | SASŪ Web Report Studio sessions time out and the Web Application server becomes unresponsive. |
A55004 |
32182 | User-defined formats are not exported from SASŪ BI Web applications to Microsoft Excel |
A55005 |
NOTE: If you install this hot fix, you must also install hot fixes:
A56005 for SAS BI Report Services 4.2_M1
A62005 for SAS Web Report Viewer 4.2_M1
A75002 for SAS Web Application Themes 9.23
A54010 for SAS Add-in for Microsoft Office 4.22 |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
A56005 for 64-bit Enabled Solaris |
SAS BI Report Services 4.2_M1 hot fix for SAS Web Report Studio 4.2_M1 |
Issue(s) Addressed: | Introduced: |
37094 | Drilling through to a SASŪ OLAP cube from a SASŪ Web application might fail |
A56001 |
37264 | SASŪ Add-In for Microsoft Office cannot display reports with a general prefilter applied |
A56001 |
37522 | Performance might be slow when viewing a SASŪ Web Report Studio report built from a SAS OLAP cube |
A56001 |
37680 | ERROR: "An error occurred processing the requested group break information" occurs in SASŪ Web Report Studio |
A56002 |
37718 | Some e-mail applications do not indicate the presence of a distributed SASŪ Web Report Studio report |
A56002 |
37818 | Prompt values might be missing for SASŪ Web Report Studio reports opened in the SASŪ Add-In for Microsoft Office |
A56002 |
37834 | ALERT - Certain conditions might contribute to poor performance when you run SASŪ Web Report Studio in Internet Explorer 6 or 7 |
A56002 |
37836 | SASŪ Web Report Studio reports based on a stored process might not honor styles when distributed |
A56002 |
37876 | SASŪ Web Report Studio performance might be slow if a data item is formatted with a user-defined format with many mapping elements |
A56002 |
30734 | Filters might be ignored when viewing detail data |
A56003 |
37720 | SASŪ Web Report Studio report fails to open if any data item in the information map does not have a default aggregation specified |
A56003 |
37933 | SASŪ Web Report Studio reports that have many conditional highlighting rules might exhibit poor performance |
A56003 |
37964 | Dynamic, multi-selection prompts do not render in SASŪ Web Report Studio if the data item is a formatted numeric category |
A56003 |
38069 | A run-time error might occur after you apply Hot Fix A55001 to the first maintenance release for SASŪ Web Report Studio 4.2 |
A56003 |
38289 | SASŪ Web Report Studio might not correctly export ranges greater than 1000 |
A56003 |
38754 | Sorting on a total column in an OLAP-based SASŪ Web Report Studio report might not work correctly |
A56003 |
38768 | ALERT - Group breaks in OLAP-based SASŪ Web Report Studio reports might not work correctly when a section filter is applied |
A56003 |
38813 | Wrong date value might be passed to a linked report in SASŪ Web Report Studio |
A56003 |
38817 | The error "Could not get entry from report repository" occurs when you save a SASŪ Web Report Studio report to a folder named with DBCS characters |
A56003 |
38822 | Linking might not work correctly for SASŪ Web Report Studio reports that display columns over multiple pages |
A56003 |
38981 | An exception occurs when you edit a text object or use conditional highlighting in SASŪ Web Report Studio from a browser with Swedish settings |
A56003 |
32182 | User-defined formats are not exported from SASŪ BI Web applications to Microsoft Excel |
A56005 |
|