Sage CRM. Sage CRM 7.2 Patch Release Notes

Transcription

1 Sage CRM Sage CRM 7.2 Patch Release Notes

2 Copyright 2014 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced, translated, microfilmed, or otherwise duplicated on any medium without prior written consent of Sage Technologies Limited. Use of the software programs described herein and this documentation is subject to the End User Licence Agreement enclosed in the software package, or accepted during system sign-up. Sage, and the Sage logo are registered trademarks or trademarks of The Sage Group PLC. All other marks are trademarks or registered trademarks of their respective owners.

3 Contents Overview... 2 Prerequisites... 2 Latest Version... 2 How to Install Sage CRM Patches... 2 Patch E... 3 Blog: Find out how to set up Sage CRM to work with Exchange Server integration Patch E Issues List... 3 Patch D Patch D Issues List March iphone app updates Additional notes on this patch (D) More information around QA Working with the Exchange Outlook plug-in with IE 11 installed on your machine Patch C Patch C Issues List Patch B Before installing Edit and save your existing Notifications Check your customizations Patch B Support Patch B Issues List Rolled-up Fixes Patch B Known Issue Patch A Patch A Issues List Patch A Patch A Issues List... 62

4 Overview This document provides details of all Sage CRM patch releases for version 7.2. Installing the most recent 7.2 patch (E) ensures that you get all of the fixes included in earlier patches (if applicable). Prerequisites You need to have Sage CRM 7.2 installed before you install the latest patch. You can find out the version of Sage CRM you are running from the Logon page, which would read CRM version 7.2, for example. Latest Version Latest Release: Version 7.2 DLL: How to Install Sage CRM Patches Use the following procedure to install the latest Sage CRM patch: 1. Back up the existing CRM eware.dll and database. The DLL is stored in the CRM installation directory, which is commonly in \Program Files\Sage\CRM\<Installation Name>\WWWRoot 2. Run the Setup.exe file. 3. When using the InstallShield wizard, you can choose to use either Windows authentication (using the credentials of the user logged in to the system at that time) or SQL Server authentication (by entering the appropriate SQL Login ID and Password). Sage CRM 7.2 Patch Release Notes 2

5 Patch E Released June 2014 Files included DLL version Outlook plugin Document plugin CTI plugin Blog: Find out how to set up Sage CRM to work with Exchange Server integration For those of you who d like to work with Exchange 2013, please find out about the configuration steps in the blog below: /18/configuring-exchange-server-integration-to-work-with-exchange-2013.aspx Patch E Issues List Note: The message reproduced in the Status column means the issue could not be reproduced on the latest version and patch. An upgrade to the latest version and patch should resolve the issue. Ref ID Area Description Status QA Cases When a user saved a Case record, if a required field wasn't filled in and if the Case SLA was set to None, the case id was incremented by 1 and all entered data was lost QA Cases On the Case screen, a user added StartTime, Endtime and Minute fields. The Minutes field (called Duration) didn't calculate the difference between StartTime and EndTime. Please note that if you create a Minutes field for Cases, you should not call it case_duration because a case_duration field already exists in the case_progress table and this would create conflicts between the two QA Cases On an integrated version of Sage CRM, if a user created a new Task from the context of a Case, the Account field wasn't automatically filled in. fields. Sage CRM 7.2 Patch Release Notes 3

6 QA Component Management It wasn't possible to record the creation of a Dashboard template using Component Manager, and then export it QA QA Component Management Component Management QA Companies / People QA Companies / People QA Companies / People QA Companies / People QA Companies / People to another install. It wasn't possible to record the creation of a Gadget template using Component Manager, and then export it to another install. When a user created a component to record the creation of a new Dashboard, the custom captions for the Dashboard weren't recorded into the component. When working with in pop-up mode, it wasn t possible to select multiple recipients by clicking different addresses in the system. After merging two companies, the Marketing tab for the merged company still contained two records, instead of just one. On 7.1h, a user created a new Person in the context of a company, and set their address to Person Only. Updating the address of the new person also updated the address of the company. When a user added more than 12 people to a company, the People grid contained duplicate people records, while others were missing from the grid. It wasn't possible to select all contacts from the Contacts list, and delete them in Sage CRM. If the component is blank then set it to be the active component. Otherwise, the generated component script will not include the translations associated with new gadgets and this will cause an error with the landing page gadget list load. Sage CRM 7.2 Patch Release Notes 4

7 QA Configuration Time zone settings for Central Time (US and Canada) were out by one hour QA Core Product On a user install with a multi-server environment, the user kept getting a 'You may need to recreate views manually error' at the same time every few days QA Core Product In Sage CRM, there was an issue with appointments ending at midnight QA Customization Adding a new field linking to a secondary entity on the Case Progress screen broke the link to Person on the screen QA Customization A user added a Date only field to the Person entity screen. The field couldn't be populated QA Customization In Administration Advanced Customization System Menus Find, clicking Save created a duplicate Solution row on a user install QA Customization After a user added a custom Opportunity list and filter box, the value of Filter Box name was populated with the custom content list, and displayed on the Opportunity Find screen. The documentation has been updated with the following note: If the Automatic Daylight Saving Time option is checked in on the server machine, then it will affect all users, even if they have not selected this option themselves in their time zone settings. This can't be fixed. The workaround is to run the following script. <script> $(document).ready(function( ){ if (crm.getarg("obn").tolower Case() === "salescommunications" && $(".CONTENTGRID tr td:first").hasclass("viewbo XCAPTION")) { $(".CONTENTGRID tr td:first").remove(); } }) </script> Sage CRM 7.2 Patch Release Notes 5

8 QA Customization It wasn't possible to change the type of a numeric field mirrored with a progress field QA Customization A user was unable to customize the Line Item screen using inline customization QA Customization It wasn't possible to create a field on Opportunity Progress and Opportunity, if the fields used the same name QA Customization When an containing a RecordAnchor was sent from a workflow rule, the record anchor didn't link back to the specified record's Summary tab QA Customization It wasn't possible to clear a case field which had been added to the case filter box QA Customization A user was unable to create an Opportunity gadget on the Dashboard after adding a custom search select advanced field on the Opportunity entity screen QA Customization It wasn't possible to create dashboard gadgets based on custom primary entities with an underscore symbol in the entity name. Sage CRM 7.2 Patch Release Notes 6

9 QA Customization A user wanted to use the Company restrictor field on Opportunity and use it as part of the Opportunity workflow. This didn't work as expected when workflow was turned on QA Customization It wasn t possible to create a workflow based on a custom Opportunity search select advanced field. The dropdown field was blank QA Customization A user wanted to create new buttons based on Quotes and Orders, and use SQL queries for these buttons QA Customization When a user clicked a custom button on the Main Menu area, the URL opened in a new page instead of being displayed in the L frame QA Customization In Administration Customization <entity>, when a user clicked 'Show Logs' for Table Level scripts, the popup window would prompt the user to log in again, and the logs weren't displayed. This is by design. The Restrictor option only works if the field that you're restricting by is on the same screen. You can't put an advanced search select field on its own onto the workflow screen. However, if you also add the comp_primarycompanyid to the workflow then the restriction will work. That is to say, you should add in a new action for Display Field for Amendment and select the comp_primarycompanyid column on the same workflow rule where you ve added in the oppo_erpaccountid action. You can set it to be read only if you like. Now, when you activate the Qualify rule, the erpaccountid will be restricted to the company selected. Quotes and orders were added to the list of possible entities in DoesSQLMatch fn. Quotes will use vquotes to query. Orders will use vorders. Sage CRM 7.2 Patch Release Notes 7

10 QA Customization Customization screens for CommunicationFilterBox were inconsistent depending on whether they were accessed from the Administration Customization area or from the inline customization mode QA Customization When a user created a DateOnly field, for example on Opportunity, and displayed it for amendment as part of a workflow rule, the field value was one day off (previous day) Customization An issue with metadata prevented custom primary entities from appearing in the User Security Profiles area QA Customization After creating a custom Wizard entity, a user was unable to change the user on a custom record QA Database It wasn't possible to create notifications QA Data Upload It wasn't possible to import an Excel file containing line feed characters QA Comms/Diary The Date picker popup window on the Recurring Appointment screen was too small QA Comms/Diary After sending an to a group, the communication under the Person tab didn't display the person's contact details QA Comms/Diary There was an issue with the default values for Date/Time fields QA Comms/Diary The Task Reminder and Time fields didn't default to a set time when selecting them. Sage CRM 7.2 Patch Release Notes 8

11 QA Comms/Diary When accessing a Company from the Recent list, when the user tried to create a new Task from the company's Communications tab, the Regarding field was filled with an unrelated Opportunity QA Comms/Diary When moving an appointment back in time, the End Time wasn't calculated properly QA Comms/Diary When creating an appointment for several attendees, including external ones, the Team CRM Calendar displays an appointment icon for the CRM user and for each attendee as well QA Comms/Diary After sending an to a group of people, if a user deleted the communication in the context of one Person, all s sent to the group were deleted QA Comms/Diary On an install, there was an issue with Date for users using Pacific Daylight Saving Time QA Documentation A user wanted to know if Solo was supported on Windows 8 tablets QA QA QA E-Marketing (SageCRM) Exchange Integration Exchange Integration A user was unable to send out a mail blast using e- Marketing. If an external attendee refused a meeting invite, they would keep on receiving invites, each time the appointment was updated. A user had an issue with Exchange Integration. The integration failed every time. This is by design. These "duplicate" icons cannot be removed as it could affect some customer installs. This issue is fixed We remind you that if the Automatic Daylight Saving Time option is checked in on the server machine, then it will affect all users, even if they have not selected this option themselves in their time zone settings. The Software Support Matrix was updated to reflect that Solo is run on versions of Sage CRM which do not support Windows 8. Sage CRM 7.2 Patch Release Notes 9

12 QA Exchange On an install, users Integration received meeting QA QA QA Exchange Integration Exchange Integration Exchange Integration notifications for past events. There was an issue with the Exchange/Sage CRM synchronization where 'Display as field' wasn't always updated properly. On a user install, Exchange integration failed when Contact Synchronization was enabled. Exchange didn't work properly because of a mismatched URL issue QA Manager A user had a query about filing s issues where the Communication record didn't always pick up the sender's address after filing QA QA QA QA Find / Advanced Find Field Level Security Field Level Security Field Level Security When using Advanced Find, the wrong error message was displayed when a user tried to set an AND/OR operator on the last row. After denying read/write access for oppo_primarycompanyid to everyone on an install, the Company tab was still available from the top content. A user wanted to hide a field from all users, except the System Administrator. The field was still visible to other users during the chart design process. If a user with no read/write access to a field on, for example, a Company record updated the record and saved it, the field would become blanked out when a user with read/write access to the field tried to edit the record next. This is by design. The 'From' address should always be associated with the user. If it is not, no is filed and you receive the following error message: 'No Users exist for this From address'. This is by design. Sage CRM 7.2 Patch Release Notes 10

13 QA Keyword Search It was not possible to do a Keyword Search on Quotes and Orders on an install integrated with Murano QA Dashboard (Interactive) It wasn t possible to create an SData gadget based on Forecasts QA Leads After converting a Lead to an Opportunity, the communications against the Lead record didn't load properly QA Leads The Lead Ratings icon is missing from the product QA Leads In the context of a Lead when a user clicked 'Add or Find this Company', the Company 'Industry' field was displayed as segment instead, and the default values set up for Company entry were ignored QA Mail Merge Mail Merge failed on the tenth and last page of a user document template QA Mobile The Date/Time picker was displayed in English in tablet mode on a French install of Sage CRM with a French OS tablet QA Mobile When working on mobile with the iphone/android theme, it wasn't possible to view the company and person linked to an existing communication, or to create a new company and person from the context of a new communication. This issue is on Murano's side. The customization package with correction is set to appear in their June release. This is by design. It seems as though the lead_rating icons were never in the product with demo data. Sage CRM doesn't have icons available for all selection fields in the product. A user could create these icons and put them in the install files. A request for enhancement can also be raised if needed. If you have a comp_industry field then lead_companyindustry maps to that, if you don't then it will map to comp_sector. Sage CRM 7.2 Patch Release Notes 11

14 QA Mobile On an account integrated with Sage 300, the Company Summary screen couldn't be displayed on iphones if a term code was added to the screen QA Mobile It wasn't possible to search for Opportunities by Close By date when working on iphone QA Mobile When working on iphone in Safari, the Date/Time display didn't match the Sage CRM user preferences QA Mobile It wasn t possible to search on an integer field on tablet QA Mobile It wasn't possible to call someone by tapping the phone number displayed on a record Summary screen on iphone QA Mobile It wasn t possible to sync the Sales Tracker app for On Premise installs integrated with Sage QA Mobile It wasn't possible to open hyperlinks on customized entity grids on the iphone/android view QA Multi Server There was an issue with an install where users kept getting logged out QA Navigation A user created a custom entity with the 'has library' option. After creating a record for the new entity, the user clicked a document, saved it without editing, and then clicked Back. The user was returned to the list of all QA Order Entry/Products library entries in the system. A user with info manager product rights with the rights to view/edit Opportunities, but with no rights to insert was unable to add new product families. Customers still need to recreate the grids in order to get this working on installs. The fields need to link to custom_lists and customid fields, rather than tabs for mobile display. Sage CRM 7.2 Patch Release Notes 12

15 QA Outlook Integ - Classic QA Outlook Integ - Classic After filing an to CRM, it wasn't possible to edit the About field for Company and Person. The option to install Outlook Plug-in was missing from the Preferences screen when the 'Allow ActiveX Document Drop' option was set to No QA Outlook Integ There were issues with the Outlook plug-in when Outlook was set to the Chinese locale QA Outlook Integ - Exchange QA Outlook Integ - Exchange QA Outlook Integ - Exchange On an install integrated with Sage 200, it wasn't possible to file an against a contact which wasn't in Sage CRM. A user with restricted access to some entities could not file s to Sage CRM. A user was unable to work with the Exchange Lite plug-in on IE QA Quotes / Orders When you created a quote, the auto-generated reference number excluded deleted quotes, meaning if you deleted a quote, it was possible to have a duplicate reference number QA Quotes / Orders The Order screen checkbox for "Include in quotes total" was set to a default Y value in Administration. Yet, this wasn't reflected on Order screens in My CRM QA Quotes / Orders On installs integrated with Sage 1000 ERP, when creating a new Quote from the context of an Account record, the Account details weren't automatically filled in. Please note the Install Outlook plugin option is only available on IE. Please look at Working with the Exchange Outlook plug-in with IE 11 installed on your machine, on the 7.2d section of this patch release notes. Sage CRM 7.2 Patch Release Notes 13

16 QA Reports If a user created an Opportunity Summary report and used 'oppo forecast' as a selection criterion of the report, the report's results weren't filtered properly QA Reports When exporting a report to PDF, line feeds were not preserved QA Reports After navigating to a report category in Sage CRM, a user received an error message after clicking the report category link in the top content QA Reports When a user filtered a report list, the top content breadcrumbs disappeared QA Reports A user had issues with generating a chart. The legends seemed duplicated because of an incorrect setting in the Chart Options QA Reports Users received a 404 error message when running a report onscreen, if the report name contained a '+' character QA Reports On a 7.0 install, if you create a report looking for opportunities closed in the previous week, you get results from the wrong year QA Reports Date formats weren't displayed properly in.csv output when the Windows Regional Settings didn't match with the Sage CRM date format QA Reports When a user ran a cross tab report, for example 'Activities Logged Report by User', the chart data and the report data didn't match QA SData Provider Users working with Office Line needed the ability to use RTDV (Real Time Data View) tables in Opportunity tabs to display orders and quotes, along with their line items. This is not an issue in 7.2 This could not be The OfficeLine team produced the customization, and the Sage CRM team unblocked it for the Opportunity entity. Sage CRM 7.2 Patch Release Notes 14

17 QA Soap Integration On an install integrated with Sage 200, there was an issue with the synchronization of deleted shipping addresses QA GCRM Account On an install integrated with Accounts, it wasn t possible to display Companies Communications view. The option errorhandling=strict is now the default setting when installing a component, which should ENH QA GCRM Integration GCRM Integration There was an issue with setting up component on integrated installs. A user had an issue with displaying Sage CRM on Mozilla QA Timings There was an issue with the Holiday Set field when creating a new SLA QA QA Translation (English prod) Translation (English prod) When adding regions to Sage CRM, the deduplication process allowed the creation of duplicates when sentence case was used. For example, 'africa' wasn't recognized as a duplicate of 'Africa'. On a user install, it was not possible to create a gadget based on a Company SData feed QA User Interface The "Home" caption (for homepage) was incorrectly translated as "Domicile" on French versions of Sage CRM QA User Interface A user wanted to use a custom favicon.ico for Sage CRM, instead of the standard IE logo QA User Interface When navigating to the Security Profiles area in Administration, a user received an error message when clicking the Security Profiles link in the top content QA User Interface A user wanted to open a case in a new tab in order to assign it to someone. reduce the amount of errors. The caption was changed to "Accueil". You can change the icon in WWWRoot\Themes\Img\def ault\icons folder. This is by design. Sage CRM can be used in one tab only. Sage CRM 7.2 Patch Release Notes 15

18 QA User Interface When inserting an inline image in an , the image didn t get inserted at the mouse cursor position. Instead, it was inserted at the bottom of the QA User Interface In 7.1 SP2, it wasn't possible to delete a user territory, even if all users in the territory had been deleted first QA User Interface A user wanted to display comp_accountid on the Company screen. This is by design. Any columns that end in 'accountid' are used for installs integrated with Sage Accounts. Users shouldn't create columns with that name. The workaround is to call the column something like 'xxx_account_id' QA QA QA User Management User Management User Management If a user logged into Sage CRM on an Android mobile device then logged in on a desktop machine, the Android Sage CRM session didn't terminate. Using Activity Tracking, it wasn't possible to track the actual length of a user login session, if said user closed the Sage CRM browser window without clicking Log off first. A user was having difficulty with setting up teams for other users on the install QA Web2lead It was not possible to use web to lead forms if a Date field was added to the screen QA Web Picker The Calendar date picker was displayed off-screen when working on a reduced browser window QA Web Services A user working with integrated Sage 300 had an issue setting up Web Services. instead. This is by design. Users should click Log off before closing the browser window. A System Administrator can also set a User Inactivity Timeout time which will automatically log off inactive user sessions after a set period of time. This issue is fixed on IE10. The user hadn't correctly marked the relevant tables as available for web service access. Sage CRM 7.2 Patch Release Notes 16

19 QA Workflow It was not possible to use workflow primary rules using a custom view. No Progress button was displayed onscreen QA Workflow When the Start Mail Merge functionality was part of a workflow, the fields for Type and Category were not displayed QA Workflow When editing a workflow, the available rules were not displayed if a user scrolled down the workflow tree QA Workflow When a user added a disabled rule to a workflow, there was no prompt to notify the user that the rule was disabled QA Workflow A user had an issue with setting up the Opportunity This could not be workflow QA Workflow It wasn't possible to change the currency of an Opportunity if a default currency value was specified in the Opportunity workflow QA Workflow When using a Send workflow action, the sent displayed the wrong record anchor. Sage CRM 7.2 Patch Release Notes 17

20 Patch D Released March 2014 Files included DLL version Outlook plugin Document plugin CTI plugin Patch D Issues List Note: The message reproduced in the Status column means the issue could not be reproduced on the latest version and patch. An upgrade to the latest version and patch should resolve the issue. Ref ID Area Description Status QA Registration Form When a user installed 7.2c, the following error occurred: "Cannot create machine ID: Machine Mac Address Can't QA QA Campaign Management Campaign Management be determined". A user with Info Admin rights was unable to use Response Set Up for outbound calls in the context of a new wave item. A user wants an outbound call list to be sorted in the same order as the group it is originally based on QA Cases When an SSA field was added to an entity page, hyperlinks pointing to a different entity were broken. This is by design. Once you have created a call list from a group, then it is not connected to the group anymore. This means editing the group's contents afterwards doesn't have any effect on the call list. When you click the button to get the next call, it orders the records like this: ORDER BY LCall_CallAfter, LCall_Attempts, LCall_AssignedToUser, Pers_LastName, Pers_FirstName. This is hard coded. An enhancement request must be raised to change the order. Sage CRM 7.2 Patch Release Notes 18

21 QA Component Management On an install with a custom component used to record customizations, it was not possible to use the QA Companies / People Interactive Dashboard. On the New Appointment screen, it was not possible to use the Advanced Search Select button (green arrow), next to the cmli_comm_personid field QA Core Product The entitywizard dll for SDK was missing from the 7.2 install files QA CTI Using CTI, if you're entering details for a Company task in the CTI frame and hang up, the mouse cursor moves away from the Details field, and you have to click it again to keep entering information QA Customization The fields added to a custom entity screen overlapped QA Customization If a user logged into Sage CRM externally, the sessions of all active users on the Interactive Dashboard were dropped QA Customization It was not possible to scroll custom ASP pages with embedded URLs on ipad devices QA Customization After creating a test table and adding some fields and captions, a user had an issue with Advanced Search Select fields in Sage CRM QA Customization A user was unable to do a search on Company after adding a custom Multi- Selection field to the Company screen QA Database A user was unable to access the Dashboard tab in My CRM because of issues with Tomcat. This can't be fixed. This was solved by changing the user's configuration. You can find out more below. Sage CRM 7.2 Patch Release Notes 19

22 QA Data Upload It was not possible to import data if required fields were blank, even though the Field Security option was deselected QA Data Upload There was an issue with the Person Fax Number field when performing a data upload QA Comms/Diary On an install with an Accounts integration, there were some performance differences between accessing the Communications tab for an Account and accessing the Communications tab for a Company QA Document Drop After setting file extension restrictions, for example,.jpg files, in Administration and Documents Documents & Reports Configuration, it is still possible to import this type of file as an attachment to Sage CRM. The feature works as expected for Document Drop QA Manager There was an issue with a.js file when working with an template containing an inline image QA QA QA QA E-Marketing (SageCRM) E-Marketing (SageCRM) E-Marketing (SageCRM) Exchange Integration It was not possible to perform an blast in Swiftpage because of an issue with addresses in dynamic groups. Using Swiftpage, it was not possible to perform an blast for a list of contacts. Following an upgrade, a user was unable to use the Marketing function "Response Setup". A customer had issues with automatic Exchange-CRM meeting updates. This is by design. An enhancement request must be raised to make this feature apply to filing s. This issue is fixed Sage CRM 7.2 Patch Release Notes 20

23 QA Exchange Integration External attendees received meeting updates notifications when the Regarding area of a meeting was updated, even when the "Include CRM info in body" option was set to QA QA Exchange Integration Exchange Integration No. A user was unable to sync some contacts to MS Outlook. It was not possible to use a secondary SMTP address for Exchange impersonation QA Facebook The Facebook tab on Company records was not displayed correctly on 7.2b QA Facebook A user was unable to access Facebook profiles on Company screens QA QA Find / Advanced Find Field Level Security Searching for All on a custom multi-select field returned no results in 7.2c. Fields created by users were set to Required by default. Sage CRM 7.2 Patch Release Notes 21

24 QA Install / Upgrade A user wanted to use different System Administrator login details to perform a Sage CRM upgrade, instead of the standard login details QA Soap Integration On an install with a Sage 200 integration, a user was unable to delete an order or quote in Sage CRM, if the record had been edited too many times QA Soap Integration On an install with a Sage 200 integration, duplicate people and addresses can be created, if you delete a Person record in CRM, then add a new Person to the Company using the same name and address QA Soap Integration On an install with a Sage 200 integration, if a user deletes an address and syncs, the address is added back to Sage CRM QA Dashboard (Interactive) A user was unable to create a new gadget on the Interactive Dashboard. This is by design. The Sage CRM installer uses the same username and password that is in the registry for Sage CRM. Workarounds are: 1. Temporarily grant the Sage CRM user more privileges and revoke them after upgrade is complete. 2. Change the username and password in the registry: Go into HKLM\SOFTWARE\Wow64 32\eWare\Config\/%instance name% and change the DatabaseUserID and DatabasePassword fields to be the username and password of the account you want to use. If you keep the old values, you can restore them into the registry after the upgrade. Note: After changing the registry, please do an IISRESET to apply your changes. This is by design. This is due to the way Sage 200 works. This is related to QA. This is by design. This is due to the way Sage 200 works. This is related to QA. Sage CRM 7.2 Patch Release Notes 22

25 QA Library and Templates When creating a new Merge document, if the Subject field was left blank, then was filled in following the validation error message, it was not possible to open the Merge document QA Licensing A business partner was unable to manually register a customer QA Mail Merge There was an issue with Mail Merge rendering for a long Word document (15 pages) QA Mail Merge A user was unable to perform a Mail Merge from a Group context QA Mobile It was not possible to edit the iphone Company grid from IE. Doing so prevented users from accessing the Company entity on iphone QA Mobile Tapping the Dashboard button on iphone brings you back to the homepage QA Opportunities It was not possible to filter the Opportunity pipeline to All QA Opportunities A user had a query about the Opportunity Tracking tab behavior QA Outlook Integ It was not possible to file s from Outlook after removing the Regarding field from the CommWebPicker screen on the Comm_Link entity. This is by design. This is due to the server, not the Sage CRM product. This is by design. You can access the mobile Dashboard only if you have configured from your desktop it first. This is by design. The Duration field on the Tracking tab displays how much time a record spends in each state. Whenever you make a change to a record, this creates a new tracking record. The last tracking record always displays the duration from the moment the tracking record was created to the current date. Sage CRM 7.2 Patch Release Notes 23

26 QA Outlook Integ A user could not use the Outlook plug-in with Outlook The user was given full admin rights to install the plug-in, then these rights were removed. As a result, the plug-in was checking for a different key value in the registry QA Outlook Integ - Exchange It was not possible to amend the Details field (comm_note) on the Communications entity QA Reports When a user created a report and selected the "Week previous" criterion, the report did not take into account User Preferences settings (My Week Starts on) QA Reports When a user unselected the "Opt out of E-marketing communications" checkbox on a Company summary screen, the value of the comp_optout field changed to "N" instead of Null QA Reports A user was unable to add oppo_stage and oppo_reason as Group By and Sort On criteria for reports QA QA QA QA GCRM Integration GCRM Integration Groups / Target Lists Security Management An integration with Murano failed following a Murano update. There was an issue with the Date Time format of synced entities. The contents of groups were not sorted using the field orders specified in Groups Settings on Sage CRM 7.2b installs with an SDATA integration. A user with no forecast rights was able to see forecasting figures displayed on the Opportunity pipeline QA Twitter A user was unable to access the Twitter tab in My CRM and from Company records. This is by design. This is due to the user's Windows environment configuration. Sage CRM 7.2 Patch Release Notes 24

27 QA User Interface On an install with a Sage 300 integration, the vertical scroll bar disappeared when clicking New Quote or New Order QA Yammer A user was unable to work with the Twitter and Yammer add-ons on 7.2a1 or 7.2b. March iphone app updates The following cases were fixed for the Sage CRM iphone app. Watch out for this upcoming update which will be announced on the Sage CRM Community. Edit April 2014: QA was removed from the Patch Release Notes. Ref ID Description Status QA A user was unable to synchronize the Calendar to the app QA In the app settings, selecting "My Assigned Contacts" or "My Team Contacts" only synced the first 200 contacts no matter how many contacts you actually have QA A user was unable to update data in the app and received the following error: "Download error, unsupported URL" QA When adding a phone contact to CRM, the address and mobile number fields weren't populated QA Deleting notes, tasks, appointments or opportunity records in Sage CRM did not delete them from the iphone app QA Users with no admin rights were unable to Update Data in the app QA The app did not support ios 7.1 Sage CRM 7.2 Patch Release Notes 25

28 Additional notes on this patch (D) More information around QA This issue was solved easily by changing the user configuration. An Advanced Search Select is always created as an integer field. This means that the field can't look up a category table that has a character code value for example. To work around this issue, create the Advanced Search Select field manually, give it a text type, and then add it to the necessary screen 1. Create a text field for your category lookup. This ensures that the database type of the field matches the codes you enter in the field. 2. Change the entry type of the field to Avanced Search Select. You can do this in the database by typing: update Custom_Edits set ColP_EntryType = 56, ColP_LookupFamily = 'ICCATG' where ColP_ColName = 'case_categorytext' where your new field is called case_categorytext for example. 3. Refresh the metadata. 4. Add the field to your Case screen. Working with the Exchange Outlook plug-in with IE 11 installed on your machine An EDOMParseError can occur if you're working with Internet Explorer 11 and try to file an in Outlook. The workaround is to: 1. Add the Sage CRM URL to the list of trusted sites in IE. You can find the correct procedure on the Microsoft website here. 2. Add the Sage CRM URL to the Tools Compatibility View Settings tab. You can find the correct procedure on the Microsoft website here. 3. Add the Sage CRM URL to your Favorites. When you delete your browsing history from Tools Internet Options Delete in the General tab, please make sure that the Preserve Favourites website data option is selected. Sage CRM 7.2 Patch Release Notes 26

29 Patch C Released December 2013 Files included DLL version Outlook plugin Document plugin CTI plugin Patch C Issues List Note: The message reproduced in the Status column means the issue could not be reproduced on the latest version and patch. An upgrade to the latest version and patch should resolve the issue. Ref ID Area Description Status QA 3rd Party Software QA Companies / People QA Companies / People QA Companies / People A customisation using MessageBlock to send an , was not populating the CC field correctly. When adding a new company and linking it to an ERP system, the content area of the Company page was not shown when the link was made. An error message, "List index out of bounds" was displayed after deleting a person. A SQL error was displayed when accessing the Company Quick Look tab after customising the case list QA Configuration Removing a check box entry on an escalation rule did not disable the rule as expected QA Configuration Time zone settings for Central Time (US and Canada) were out by one hour QA Core Product There was a typo in a document library error The documentation has been updated with the following note: If the Automatic Daylight Saving Time option is checked in on the server machine, then it will affect all users, even if they have not selected this option themselves in their time zone settings. Sage CRM 7.2 Patch Release Notes 27

30 message QA Core Product It was possible to create a duplicate user name when one of the users was set to disabled QA Core Product Screen contents were not displaying correctly after resizing the browser in an integrated Sage CRM system QA Core Product An error message was displayed when using the "Add File" feature in Chrome QA Core Product On-screen notifications were not displaying when the field, "Escalation tuned for", was set to "System Performance" QA CTI An error occurred when using group pick-up to take an incoming call using CTI QA CTI It was not possible to use the CTI plug-in due a permissions issue QA Customization Company and person default values were not populated on a custom tab QA Customization A user was logged out of Sage CRM when selecting a link to a list from a custom entity QA Customization A url set up in Custom Content was not displaying correctly QA Customization A customised Date Only field was being deleted rather than hidden QA Customization It was not possible to clear a case field which had been added to the case filter box QA Database A stored procedure used during upgrade to 7.2 required improvement QA Database System log files were larger than expected. Sage CRM 7.2 Patch Release Notes 28

31 QA Comms/Diary In a localised French system, a communication was linked to a case and saved. When the link was revisited and selected, an opportunity rather than the linked case was displayed QA Comms/Diary A communication record for an external attendee on an appointment was not visible from the Quick Look tab QA Comms/Diary A customised user select field was not displaying correctly on an ipad QA Comms/Diary When creating a follow-up communication from the context of a lead, which was selected from the recent list, the related company and person details were not populated on the communication screen QA QA QA E-Marketing (SageCRM) Exchange Integration Find / Advanced Find A SQL error occurred when selecting "Click here to view the recipients of the E- Marketing ". Appointments were not synching from CRM to Exchange. The search results from a person search where the e- mail restriction field was checked, were still showing a list of all people - not just people with the restriction flag set QA Find / Advanced The advanced search select Find field on a custom entity was being incorrectly populated rather than left blank QA Install / Upgrade Selected report columns changed when using the Previous button in the report builder QA Soap Integration Account contact details were incorrectly updated after changing a custom system parameter setting QA JavaScript API It was possible to activate a script from the company name field. Sage CRM 7.2 Patch Release Notes 29

32 QA Leads A lead could not be converted to an opportunity because the Opportunity Person Name field was blank and not auto-populating QA Mail Merge "docm" and "dotm" files were not showing in the document library QA Mobile An template was not showing as a merged when viewed from an ipad QA Multi Server It was not possible to log into Sage CRM in a multi-server environment with a configuration of: server 1 server 2 with Load Balancing enabled QA Navigation The user was not returned to the company context after using the communication follow-up check box QA Notification Case notifications were not correctly triggered by workflow QA Opportunities Accessing quotes related to an opportunity, from the context of a custom tab, lost the link to the opportunity QA Outlook Integ - Exchange An communication record was not displaying in the company context QA Quotes / Orders It was not possible to clear the company and person details from the Find Order screen QA Related Entities A French translation was missing when adding a new custom tab using the "relatedcompanieslist" action QA Reports Incorrect communications were shown in report output on a German Windows 2008 install QA Reports Arabic data was not displaying correctly in reports QA Reports There was an error in report output when "Show original This is by design. The user must click "Add or find person" before converting the lead to an opportunity. This issue is closed. "docm" files work in 7.2c. "dotm" files are not supported. This issue is closed. The Sage CRM client is not fully supported on the ipad. This issue is could not be Sage CRM 7.2 Patch Release Notes 30

33 currency values" was selected QA Reports Incorrect integer and date field format displayed in an opportunity report QA QA QA QA QA QA QA QA GCRM Integration E-Marketing (Swiftpage) E-Marketing (Swiftpage) Groups / Target Lists Groups / Target Lists Groups / Target Lists Groups / Target Lists Translation (English prod) Synchronisation failed with an error on the Credit Limit field in an OfficeLine integrated system. When carrying out an E- Marketing blast, the e- mail was taking duplicate records into account and therefore exceeding the daily E-Marketing allowance. E-Marketing statistics were not synchronising with Sage CRM as expected. A SQL error was displayed when editing a group based on opportunities. The Exclude All option was not working correctly when creating a new group within E-Marketing. An error was generated when creating a new group from the Find screen. No data was returned when creating a group of leads where the last name field was left blank - even though this field had been customised so that it was not required. Translations were not displayed correctly when < or > was used in the translation of a caption code QA Web Services MS Visual Studio could not connect to the CRM web service WSDL QA Web Services An error occurred when trying to insert an AR customer from Sage 300 into Sage CRM QA Workflow The initiation of an escalation rule was resetting the duration time in the tracking tab. In addition, a custom This is fixed. The first issue is by design. The second issue could not be Sage CRM 7.2 Patch Release Notes 31

34 check box field was not being updated QA Workflow A customised case field showing addresses was not restricting the addresses to the current context when used within workflow. Instead, a list of all addresses was displayed QA Workflow A custom label, which was part of an Execute SQL workflow action, was incorrectly displayed on the case screen. This is by design. Please set the "Show confirmation message" to "No" on the workflow action. Sage CRM 7.2 Patch Release Notes 32

35 Patch B Released October 2013 Files included DLL version Outlook plugin Document plugin CTI plugin Before installing Many changes have been implemented with this release. Before installing this patch, please be aware of the following: Edit and save your existing Notifications Changes have been made to improve notifications. However, you will need to edit and save all of your existing on-screen notifications to apply this fix. As a reminder, System Administrators can create and edit on-screen notifications for their users in Administration Customization Entity Notifications. See QA in the Issues List for more information. Check your customizations This patch release introduces changes to way ASP pages are rendered in Sage CRM. These changes mean that customizations not using the GetPage() method will break when Sage CRM 7.2b is installed. What has changed? In Sage CRM 7.2, we introduced the removal of framesets in order to improve the Sage CRM User Interface. Sage CRM 7.2b further improves the User Interface by ensuring that the top content and left-hand menu of CRM (the L ) is always rendering correctly. Previously ASP pages used to be rendered within a frame and only needed to render the horizontal tabs (if any) and the page content itself. Now, ASP pages are rendered within the main browser window and so they need to render the entire page, "L" included. To do so, Sage CRM 7.2b now only uses the API method called CRM.GetPage to render pages. Sage CRM 7.2 Patch Release Notes 33

36 Sage CRM 7.2b now only uses the API method called CRM.GetPage to render pages. This change means that all pages and customizations must use the CRM.GetPage method in order to work with Sage CRM 7.2b. The following issues may be encountered for pages not using this method: The L is missing In this case the CRM.GetPage method is probably not getting called. It is likely that your asp page is generating HTML and sending it directly to the browser using Response.Write calls. These calls need to be changed to CRM.AddContent calls instead, this will add the HTML strings to a buffer which can be written to the response stream with Response.Write(CRM.GetPage());. The CRM.GetPage method will output the entire HTML document, including all the HTML necessary to render the L and the top tabs. There should be nothing written to the stream before or after it. There should only be one Response.Write call. You can read more about the GetPage and AddContent methods in the online developer help. Too many L in the page You may see the "L" appear in pop-up windows and within iframes where you previously did not see it. In these cases you will need to change your GetPage calls to GetPageNoFrameset calls instead. GetPageNoFrameset is a new method, its usage and function is exactly the same as GetPage except it does not render the "L". Sage CRM 7.2 Patch Release Notes 34