A54010 |
SAS Add-in for Microsoft Office 4.22 |
Issue(s) Addressed: | Introduced: |
36620 | The side-by-side custom report layout might change after using Send To in SAS� Enterprise Guide� |
A54001 |
37004 | SAS� Enterprise Guide� might exit without warning when using the Create Format task |
A54001 |
37658 | Percentage values are not returned correctly for certain regional settings in the SAS� Add-In for Microsoft Office |
A54001 |
37684 | The SAS� Add-In for Microsoft Office cannot display reports when SAS� Web Report Studio is deployed in a clustered environment |
A54001 |
37727 | Microsoft Excel files saved in SAS� folders are not automatically refreshed when opened |
A54001 |
37750 | SAS� reports opened in Microsoft Excel using the SAS� Add-In for Microsoft Office might not retain formatting for measures |
A54001 |
37771 | A SAS� Web Report Studio report opened in Microsoft Excel might not display formats correctly |
A54001 |
37772 | Conditional highlighting might be partially applied when a SAS� Web Report Studio report is opened in Microsoft Excel |
A54001 |
37795 | Option to display labels instead of variable names is not honored for SAS� Information Maps in the SAS� Add-In for Microsoft Office |
A54001 |
37956 | The Mappings file in the Migration Wizard of SAS� Enterprise Guide� 4.2 cannot be used |
A54001 |
37994 | SAS� Enterprise Guide� cannot use the Assign Project Library task for DBMS libraries that use a local server connection |
A54001 |
38124 | ALERT - SAS� Add-In for Microsoft Office might not correctly apply the NLNUM format in SAS� Web Report Studio reports |
A54001 |
36814 | SAS® Add-In for Microsoft Office might cause Microsoft Excel to crash after performing a show detail request against a SAS® OLAP cube |
A54003 |
37867 | Certain filters in the Query Builder might parse incorrectly in SAS� Enterprise Guide� running against SAS� on z/OS |
A54003 |
37916 | Prompts might generate errors after migrating to SAS ® Enterprise Guide 4.2 |
A54003 |
38220 | SAS� Information Maps with filters do not migrate properly from the SAS� Add-In for Microsoft Office 2.1 to the SAS Add-In for Microsoft Office 4.2 |
A54003 |
38249 | Information maps that use shared prompts do not display correctly in the SAS� Add-In for Microsoft Office or in SAS� Enterprise Guide� |
A54003 |
38439 | Stored processes are missing from portlets after being updated with SAS� Enterprise Guide� |
A54003 |
38675 | A SAS Report might display duplicate graphics in SAS� Enterprise Guide� |
A54003 |
38876 | Differences between importing data in SAS� Enterprise Guide� 4.1 versus SAS Enterprise Guide 4.2 |
A54003 |
39021 | Microsoft Word stops working when you open a Read-only document and the SAS� Add-In for Microsoft Office is installed |
A54003 |
39045 | SAS� Web Report Studio report might not render correctly in native French Microsoft Excel when the NLNUM format is applied |
A54003 |
39087 | Unable to Copy to Server from certain Microsoft Excel files in the SAS� Add-In for Microsoft Office |
A54003 |
38705 | SAS� Enterprise Guide� tasks do not take advantage of in-database processing |
A54005 |
39146 | Variable order might not be retained with List Data task in SAS� Enterprise Guide� |
A54005 |
39204 | Cannot save changes to VBA code in Microsoft Excel .xla files with SAS� Add-In for Microsoft Office |
A54005 |
39388 | An error occurs in SAS� Enterprise Guide� 4.1 and 4.2 when you use DBMS data sets that are stored in SAS folders |
A54005 |
39389 | Dynamic date values in a SAS� Web Report Studio report are not formatted correctly in the SAS� Add-In for Microsoft Office running in a French locale |
A54005 |
38357 | SAS� Stored Processes created using SAS� Enterprise Guide� might fail to run when the language is set to Norwegian |
A54007 |
39600 | Draw Border tool does not stay active in Microsoft Excel when you run the SAS� Add-In for Microsoft Office |
A54007 |
39608 | Exception returned when using the SAS� Add-In for Microsoft Office to refresh a graph that has been formatted in Microsoft Word |
A54007 |
39893 | Datetime values might display as ####### in PivotTables when using the SAS� Add-In for Microsoft Office |
A54007 |
40041 | SAS� Enterprise Guide� and the SAS� Add-in for Microsoft Office might stop responding when refreshing a stored process with cascading prompts |
A54007 |
40130 | Errors might occur when you run a project after migration in SAS� Enterprise Guide� |
A54007 |
40519 | Performance is slow when opening a SAS� Information Map using the SAS� Add-in for Microsoft Office |
A54008 |
40584 | An error occurs when the SAS� Add-In 4.3 for Microsoft Office and the SAS� Add-In 4.2 for Microsoft Office are installed side-by-side |
A54008 |
38061 | An application error might occur after modifying the Logistic Regression task in SAS� Enterprise Guide� |
A54010 |
39599 | SAS� Add-In for Microsoft Office cannot open an information map if a data item includes an apostrophe in its ID |
A54010 |
40476 | SAS� Stored Processes created using SAS� Management Console might fail to run when the language is set to Norwegian |
A54010 |
40616 | Information maps that include a prompted filter with a dynamic list might fail to run in the Norwegian locale |
A54010 |
41470 | Option to display filter information in Microsoft Excel does not work for information maps opened with the SAS� Add-In for Microsoft Office |
A54010 |
41471 | SAS� Add-In for Microsoft Office does not persist the order in which data items are selected from an information map |
A54010 |
41544 | Viewing properties for an unassigned DBMS library in SAS� Enterprise Guide� might cause certain library options to become unusable |
A54010 |
41586 | Unable to type formatted date values into the filter dialog |
A54010 |
41918 | SAS� Add-In for Microsoft Office appears to stop responding when opening a Microsoft Excel file that contains data to be refreshed on open |
A54010 |
NOTE: You must have the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update patch applied to your system. Refer to SN-40703 for more information and a link to download this patch. |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |