Sage R2 Release Notes

Transcription

1 Sage R2 Release Notes 26/03/2014 Sage (UK) Limited, 2014 Page 1 of 7

2 Sage R2 Release Notes About these release notes This document contains essential information for Sage R2. You must read this document before you use Sage R2. This document contains a summary of known issues and a summary of any issues fixed since Sage Service Pack 1. All other documents, including the Deployment and Installation Guide, can be found on the Sage Support site. Note: The Sage 200 CRM Guides can be found on the DVD in the Sage 200 CRM Documentation Folder. The following documents can be found on the site: On Premise Guides Sage 200 On Premise Deployment and Installation Guide 2013 R2 Sage 200 On Premise System Requirements Installing the Self Service web site on an external server Sage 200 BI Cubes and Reports Sage PayPort for Sage R2 Upgrading Sage 200 CRM 2013 R2 Online Guides Sage 200 Deployment and Installation Guide 2013 R2 Sage 200 Sage 200 Online System Requirements 2013 R2 Sage 200 Online Customer Guide 2013 R2 For both versions Workspaces in Sage 200 Best Practice Guide for R2 Any updates made to these guides following the release of R2 will be uploaded to the support website. 26/03/2014 Sage (UK) Limited, 2014 Page 2 of 7

3 Demonstration Data CRMData.bak CRMSelfService.bak Sage200DemoEnvironment.bak BIDemoData.bak Sage200Manufacturing.bak These backup files provide two distinct demonstration environments: Sage 200 Financials and Commercials, with optional CRM and Business Intelligence. Sage 200 Manufacturing. Installation We have made changes to the installation steps for Sage R2. These changes have been documented in Chapter 4 of the Sage 200 On Premise Deployment and Installation Guide released with Sage 200 R2 (publication number 14512). Important Note: You must log in as an Administrator when installing Sage R2. You must also log in as an Administrator if you add modules at a later date. If you do not log in as an Administrator you may experience errors generated by a file named AutoUpdatesRegistrationCA.exe during the installation routine. Windows Installer Error We are aware of an intermittent error with installations on Windows 2012 and 2012 R2. The error occurs when running the Setup.exe file. As part of the installation routine, Sage 200 attempts to install the Visual C++ Runtime Libraries. It is possible that you will see the following message: If this message appears you should not continue with the installation as the Visual C++ Runtime Libraries will not be installed correctly. If the message appears: 1. Click OK. 2. Cancel out of the installer. 3. Run the installer again by clicking on the Setup.exe. Error installing Sage 200 CRM 7.2b on 64 bit machines 26/03/2014 Sage (UK) Limited, 2014 Page 3 of 7

4 We are aware of an error that can occur when installing Sage 200 CRM 7.2b. If the message appears: 1. Locate the Application Request Routing file, from the location specified in the error message. 2. Right-click on the file and select Run as Administrator. 3. Once the installation has completed, perform an IISReset. 4. Re-install CRM 7.2.b by clicking on the Setup.exe. InstallSettings.xml is not updated on the server We have identified an intermittent issue where the InstallSettings.xml file in C:\Sage\Installers isn t being updated on the server if a change has been made. Before installing clients from the Sage share, you must review the xml file to ensure that all required modules have been selected. If the flags in the InstallSettings.xml files have not been updated to indicate that a module has been added, you should run the Setup.exe file again, selecting the required modules. Sage 200 Manufacturing Stock Projection Details We have replaced some charting controls in Sage R2. This improves compatibility with Windows 8, Windows 8.1 and Windows Server This change also provides a consistent look and feel with other areas of Sage 200. As a result of these changes, the following graphs are not available: Graph tab on Stock Projection Item Details Graph tab on Monitor Operation Times Histogram tab on Monitor Operation Times This prevents you from using the options in those Workspaces (for example, opening, saving, Copy to Clipboard, print and the tools to change the display of the charts). MRP Unable to amend the first recommendation on the system When the user runs MRP within Manufacturing for the first time, the MRP numbering sequence runs from MRP000000, rather than MRP As a consequence of this, the first recommendation will not be selectable on the MRP Recommendations form. To renumber the recommendations you must run the MRP twice on a new dataset, before actioning or maintaining any recommendations. Subsequently, MRP need only be run once. Report Designer (Online Users Only) Unhandled exception error when opening Report Designer for the first time We have been made aware that the following error may be seen when opening the Report Designer for the first time: Help URL '' is not valid. Parameter name: url. To fix this issue, click OK to close the message and reopen Report designer. You will be prompted to log in to SageID. Enter your SageID details and Report Designer will open correctly. Please note: This message may still appear if you have accessed modules within Sage 200 prior to accessing Report Designer. 26/03/2014 Sage (UK) Limited, 2014 Page 4 of 7

5 Sage 200 Suite Tools Sage R2 uses a new version of ManufacturingCSVFileConversion.exe The latest version of the CSV Conversion Tool is incompatible with Sage R2. If you attempt to use the previous tool, the following message appears: You must ensure that you have downloaded the latest version of the tool from the Support website. Issues Fixed The list below contains details of the live issues reported to us, by our Business Partners and Customers and internally reported issues. It is organised by module. The R2 release also includes any fixes that were made in Sage Service Pack 1. Module Issue Tracking System No. (where applicable) Description SAA Core We have fixed an issue where the removal of the authorisation to a feature caused Sage 200 to crash. We have fixed an issue with the incorrect financial year start date on new datasets. This update addresses an issue which may have affected BI and how the BI Admin tool reads the data. WTE 966 & 2841 NL 2780 SOP 4730 PA 4731 POP 5600 Unexpected exception messages appeared when submitting timesheets outside of permitted dates. For example; Number Message: The date is outside the acceptable range and cannot be accepted. Please correct the date. This issue has been fixed. We have fixed an issue when an error message appears when a nonposting nominal account is added to projects or templates Prior to this release, project postings were not using the latest exchange rates when entering a SOP order. This had the potential to affect the recorded profitability figures for that project. We have fixed an issue where incorrect actual revenue postings were made when raising a sales order against a project. Previously, the correct value was posted to the sales ledger, but incorrect values were recorded against the project. In previous versions of Sage 200, over invoicing a partially received purchase order could create stock discrepancies. This issue is now resolved. Manufacturing 26/03/2014 Sage (UK) Limited, 2014 Page 5 of 7

6 WOP 5669 & 5682 ST 5687 We have resolved an issue where workspaces were not working correctly when using Internet Explorer 11. Prior to this release, Manufacturing users experienced issues with details not being saved correctly on the Manufacturing tab on the Enter New Stock Item window. This has been resolved. Report Designer 5089 We have fixed an issue where duplicate lines are created when exporting reports to CSV format, following the installation of report designer v When exporting any transactional report to CSV from Sage 200, these duplicates appeared at the bottom of each 'group'. 26/03/2014 Sage (UK) Limited, 2014 Page 6 of 7

7 Developer Programme Scripting 5580 We have fixed an issue where forms that use FormSaveBehaviorAsync, dispose or reset their BusinessObjects before EndSave() fires. The EndSave event fires 'too late' for third party developers to be able to do some processing with the form's Bound Objects if the form is using FormSaveBehaviorAsync. Other fixes SDBX (Online only) Performance We have made further improvements to the 10MB limit in SDBX packages by changing the way that it uploads to Sage 200 server. The maximum compressed size of the SDBX file is now 50MB. When uncompressed, the files must not be over 120MB. We have fixed a memory issue when importing large numbers of prices in the Price Book We have added support for the archiving of stock items with very large numbers of transactions. We have made speed improvements to timesheet entry on datasets with large numbers of existing timesheets. Database Upgrades We have fixed an issue where database upgrades failed when the counter table exceeded the maximum INT value. 26/03/2014 Sage (UK) Limited, 2014 Page 7 of 7