Browse By Tags

Summary: Opening a custom URL in a new window may result in a script error in v7.2. Symptoms: A custom URL can be added to the main Find menu by nanvigating to Administration -> Advanced Customisation -> System Menus ,and selecting the Find menu option. In order to have the URL open a website in...

Summary: When using a low screen resolution (800x600) and a gridsize higher than 10 (i.e. 25), the focus for UserContactList (MyCRM -> Contacts) will scroll down to the last row of the grid. Symptoms: The customer wanted the focus set to the top of the grid. Work around / Resolution: There’s...

Summary: Issue with Document drop not working as it is not loading properly Symptoms: The Document drop icon is missing but the text remains. Dragging a document onto the icon does nothing. Cause: A request to load some Javascript needed by the plugin was resulting in an error 500. This happened because...

Summary: Users may experience a delay when attempting to load screens that are launched using the jQuery load() function. This includes the Workflow and New Line Item screens. Symptoms: Poor performance may be seen when loading certain screens, especially when the user is not accessing CRM on a local...

Summary: Commenting out the last line of an OnChange script on the CommWebPicker screen may result in a scripting error in the Outlook plugin. This applies for both the Exchange plugin and the Outlook Lite plugin. Symptoms: Selecting a Company record when filing an email from Outlook may result in the...

Symptoms: On the New Appointment screen, selecting the green arrow next to the Person: field (Cmli_Comm_PersonId) may result in the following error being displayed: An error has occurred in the script on this page Object doesn’t support property or method 'NavPopupUrlcmli_comm_personid'...

Summary: An issue may occur in versions 7.1 and 7.2 of Sage CRM whereby a JavaScript error appears when attempting to file an email from a contact that does not exist in CRM. This issue will only occur in instances of Sage CRM that are integrated with Sage 200. Symptoms: The issue can be reproduced when...

Summary: Following an upgrade to 7.2g, users may experience a JavaScript error on their dashboard. This error prevents the dashboard gadgets from loading. Symptoms: The following error message may appear on-screen: Error text reads: The application could not initialise.Please contact your Administrator...

Summary: After adding the lead_opened datetime field to a web to lead form, leads may be created in Sage CRM with a default time of midnight UTC. The date portion of the datetime field will be unaffected. Symptoms: The issue can be reproduced by creating a web to lead form containing the lead_opened...

Summary: A script error may occur when adding Custom Content scripts to the Top Content screens for custom entities. Symptoms: On adding some basic JavaScript to the Top Content area for a custom entity, a range of errors may be displayed. These can include the following: Unterminated string constant...

Summary: An issue may arise when users have the "Use AM/PM" option set to Yes, and save a time value with no space between the time and the AM/PM part. Symptoms: As an example, if a user were to save the time an opportunity were opened as "12:00PM" (as distinct from "12:00 PM"...

Summary: By default, numeric fields in Sage CRM (fields with an EntryType of 32) are not displayed using separators of for multiples of 1,000. Separators are only used for Currency fields within the system. Customers may wish to use thousand separators in the product; these can be added using a straightforward...