C46026 |
SAS Add-in for Microsoft Office 4.305 |
Issue(s) Addressed: | Introduced: |
41522 | Localization updates available for SAS® Add-in for Microsoft Office 4.305 |
C46002 |
42193 | Stored Process Wizard screen not displayed properly under some languages |
C46007 |
42194 | 'Save' window does not open in SAS® Enterprise Guide 4.305 for Hebrew |
C46007 |
42602 | Task list is empty when using the SAS® Add-In for Microsoft Office in the Hebrew locale |
C46008 |
43195 | Filter Information Map Dialog is incomplete in SAS Add-in for Microsoft Office 4.3 in Swedish environment |
C46012 |
43196 | Very small buttons in the SAS Add-in for Microsoft Office 4.3 Outlook Gadget Manager in Danish or Turkish environment |
C46012 |
43549 | Tasks will not run properly in Hebrew due to encoding issue with footnotes |
C46015 |
41548 | In SAS Enterprise Guide® 4.3, the Stored Process Wizard will not allow the Source File Path on z/OS® to use an hfs file |
C46016 |
43696 | Length of character computed column from SAS® Information Map might be truncated to 32 |
C46016 |
43796 | Plot with one-step-ahead predictions and future forecasts is not available in ARIMA task in SAS® Enterprise Guide 4.3 |
C46016 |
44417 | 'Insert columns' selection is incorrectly translated to 'Copy' |
C46019 |
45008 | Missing OK and Cancel buttons when attempting to filter and sort an information map in specific languages using the SAS® Add-In for Microsoft Office |
C46023 |
45250 | DBCS functions are not listed on "New Computed Column" Window |
C46023 |
45916 | "Show Member Property" on an OLAP cube produces an error in SAS® Enterprise Guide 4.305 and SAS® Add-in for Microsoft Office 4.305 |
C46025 |
46279 | "Options" selections in Stored Process Wizard is incomplete in Polish environment |
C46026 |
NOTE: This hot fix is applicable to systems with one or more of the following languages installed:
Chinese (Simplified), Chinese Traditional (Taiwan), Chinese Traditional (Hong Kong SAR), Danish, Dutch, French, German, Hebrew, Italian, Japanese, Korean, Polish, Russian, Spanish, Swedish, Turkish |
NOTE: You must also install hot fix C46032 to fully implement fixes in this hot fix. |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |
C46032 |
SAS Add-in for Microsoft Office 4.305 |
Issue(s) Addressed: | Introduced: |
35656 | SAS® data set associations might be removed after copying and repositioning worksheets in Microsoft Excel |
C46001 |
40519 | Performance is slow when opening a SAS® Information Map using the SAS® Add-in for Microsoft Office |
C46001 |
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 |
C46001 |
40591 | SAS menus do not appear in Microsoft Office programs when SAS® Add-In 4.3 for Microsoft Office is installed on 32-bit computers with Wow6432Node |
C46001 |
40698 | Missing data when creating a slice from a SAS® OLAP cube |
C46001 |
41213 | Unformatted values are shown with the SAS® Add-In for Microsoft Office |
C46001 |
41216 | Cell formatting is removed after refreshing when output parameters are specified in the SAS® Add-In for Microsoft Office |
C46001 |
41217 | Exception returned when a format contains a numeric in the SAS® Add-In for Microsoft Office |
C46001 |
42041 | Error creating a custom filter in SAS® Enterprise Guide® or the SAS® Add-In for Microsoft Office when the data item name contains blank spaces |
C46001 |
42064 | A copied Microsoft Excel worksheet might not retain SAS content from the original worksheet |
C46001 |
38061 | An application error might occur after modifying the Logistic Regression task in SAS® Enterprise Guide® |
C46003 |
39599 | SAS® Add-In for Microsoft Office cannot open an information map if a data item includes an apostrophe in its ID |
C46003 |
40673 | Publish task might randomly generate an error in SAS® Enterprise Guide® |
C46003 |
41171 | The SAS® Add-In 4.3 for Microsoft Office does not display the SAS® menu in Microsoft Office 2003 programs |
C46003 |
41204 | Titles for task results might not display correctly in SAS® Enterprise Guide® |
C46003 |
41336 | Error occurs when you try to build a query or filter on a data set in SAS® Enterprise Guide® |
C46003 |
41548 | In SAS Enterprise Guide® 4.3, the Stored Process Wizard will not allow the Source File Path on z/OS® to use an hfs file |
C46003 |
41583 | The error "Invalid object DNA" occurs when you run migrated projects in SAS® Enterprise Guide® 4.2 |
C46003 |
41586 | Unable to type formatted date values into the filter dialog |
C46003 |
40587 | Error retrieving results when getting values for some prompts in SAS® Enterprise Guide® |
C46006 |
41470 | Option to display filter information in Microsoft Excel does not work for information maps opened with the SAS® Add-In for Microsoft Office |
C46006 |
42043 | Cannot create a custom filter for missing dates or datetimes when opening an information map in SAS® Enterprise Guide® or the SAS® Add-In for Microsoft Office |
C46006 |
42098 | Icons might display for View instead of List or Details in SAS® Enterprise Guide® |
C46006 |
42310 | Applying Hot Fix C44003 causes a transcoding error when running a stored process on non-English editions of SAS® Enterprise Guide® 4.3 |
C46006 |
42584 | Cannot change input data source for a task in the SAS® Add-In for Microsoft Office |
C46006 |
42585 | Advanced filter is removed after migrating a SAS® Add-In 2.1 for Microsoft Office file to SAS Add-In 4.3 for Microsoft Office |
C46006 |
42588 | Opening a large information map in SAS® Enterprise Guide® might display empty prompts |
C46006 |
42589 | Prompts do not display in Microsoft Excel when opening an information map that uses a prompted stored process |
C46006 |
42590 | Formats might not be displayed in charts when connected to a SAS® 9.3 OLAP Server |
C46006 |
42602 | Task list is empty when using the SAS® Add-In for Microsoft Office in the Hebrew locale |
C46006 |
43964 | The message "The SAS Metadata server has SAS 9.3 stored processes that are not supported in this release of Enterprise Guide" appears |
C46006 |
38888 | Opening a Private OLAP Server definition might cause SAS® Enterprise Guide® to work incorrectly |
C46010 |
41915 | Prompt values are duplicated when opening OLAP-based SAS® Web Report Studio reports in the SAS® Add-In for Microsoft Office |
C46010 |
41969 | Application error when creating multiple line plots in SAS® Enterprise Guide® |
C46010 |
42316 | Line legend options might apply to the bar legend for the Bar-Line Chart task in SAS® Enterprise Guide® |
C46010 |
43127 | "Access is denied" when attempting to run the switcher utility with the SAS® Add-in for Microsoft Office |
C46010 |
43128 | Forced out of edit mode when using the SAS® Add-In for Microsoft Office to edit a SAS® table in Microsoft Excel |
C46010 |
43192 | taskeng.exe window appears when running a SAS® Enterprise Guide® project using Visual Basic Script |
C46010 |
43901 | SAS® Enterprise Guide® projects might fail and result in the error "SDS failed to provide the decoder for the data set" |
C46010 |
42693 | The SAS® Add-in for Microsoft Office generates an error when you invoke Microsoft Excel from a Web application |
C46011 |
44629 | SAS® Enterprise Guide® might encounter a problem connecting to a SAS application server in a SAS grid environment |
C46011 |
13604 | WHERE clause might be too long and cause syntax errors in SAS® Enterprise Guide |
C46014 |
42623 | Data items with the same name from different tables might be switched when modifying the Import Data task in SAS® Enterprise Guide® |
C46014 |
42975 | Scheduled projects that contain a condition might stop responding in SAS® Enterprise Guide® |
C46014 |
43047 | "File or Directory" prompt type does not work when the workspace server is on the same machine as SAS Enterprise Guide |
C46014 |
43331 | After installing SAS® Add-in for Microsoft Office, problems occur when multiple user accounts open Microsoft Office |
C46014 |
43696 | Length of character computed column from SAS® Information Map might be truncated to 32 |
C46014 |
43737 | SAS® Stored Process prompt list is not sorted by unformatted value if SAS® Enterprise Guide® created the prompt |
C46014 |
43796 | Plot with one-step-ahead predictions and future forecasts is not available in ARIMA task in SAS® Enterprise Guide 4.3 |
C46014 |
43888 | Prompt list might not be sorted correctly in SAS® Enterprise Guide® |
C46014 |
44352 | Code generated by the Query Builder might result in syntax errors due to incorrect parsing |
C46014 |
46013 | Formatting might be removed when sending results from SAS® Enterprise Guide® to Microsoft Excel |
C46014 |
46087 | Opening a protected Microsoft Word document with Microsoft Office 2010 might display an exception in the SAS® Add-In for Microsoft Office |
C46014 |
43878 | An Application Error might occur when using the Logistic Regression task in SAS® Enterprise Guide® |
C46018 |
43884 | Data sets in migrated SAS® Enterprise Guide® projects might have incorrect creation and modification dates |
C46018 |
43948 | A filter string that contains the IN operator might fail after migration from the SAS® Add-In 2.1 for Microsoft Office |
C46018 |
44391 | Disabled row numbers reappear after migrating workbook to the SAS® Add-In 4.3 for Microsoft Office |
C46018 |
44503 | Unable to migrate or refresh a worksheet with a simple filter when using the SAS® Add-In for Microsoft Office |
C46018 |
44563 | Formula no longer works in Microsoft Excel after migrating a worksheet from the SAS® Add-In 2.1 for Microsoft Office to version 4.3 |
C46018 |
44580 | "Unable to render the data view" when adding a filter to a table in Microsoft Excel using the SAS® Add-In for Microsoft Office |
C46018 |
44581 | Table formatting might be lost after refreshing a table that has been migrated from the SAS® Add-In 2.1 for Microsoft Office to version 4.3 |
C46018 |
44879 | The error "Unable to render the data view" might appear when you filter or refresh data within Microsoft Excel |
C46018 |
44933 | Row numbers display in output data after migrating the workbook to the SAS® Add-In 4.3 for Microsoft Office |
C46018 |
43807 | Conditional highlighting for negative values might not be applied to reports opened in SAS® Enterprise Guide® or the SAS® Add-In for Microsoft Office |
C46020 |
44226 | Reports that contain empty tables might not correctly display in SAS® Enterprise Guide® and the SAS® Add-In for Microsoft Office |
C46020 |
44856 | "Cannot open this item" might appear when opening e-mail in Microsoft Outlook when the SAS® Add-In for Microsoft Office is enabled |
C46020 |
45695 | Using an analysis variable with all missing values prevents the summary statistics task from running |
C46020 |
44984 | Graphs generated by SAS tasks in the SAS® Add-in for Microsoft Office might generate incorrect results when input data is filtered in Microsoft Excel |
C46022 |
45434 | Dashboards created with SAS® BI Dashboard 4.31 cannot be opened in Microsoft Outlook using the SAS® Add-In 4.3 for Microsoft Office |
C46022 |
45435 | Task template error might appear when refreshing SAS® Add-In for Microsoft Office content |
C46022 |
46403 | Properties set from the Manage Content window might be ignored in the SAS® Add-In for Microsoft Office |
C46024 |
46428 | "Index was outside the bounds of the array" appears when viewing details for a Microsoft Excel PivotTable that contains more than 256 columns |
C46024 |
15842 | Workbooks remain in the Visual Basic Editor when you install the SAS® Add-In for Microsoft Office |
C46027 |
46633 | Manually entering a date value in the Filter and Sort task might not return the correct results in the SAS® Add-In for Microsoft Office |
C46027 |
41512 | Run-time error is generated when Report Filter is populated in a PivotTable with the SAS® Add-In for Microsoft Office |
C46028 |
49000 | "PivotTable was not found" might occur after refreshing SAS Content from the Manage Content window when a copied worksheet is active |
C46032 |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |