Browse By Tags

  • Wiki Page: 492-16649 - Unable to use a multiplication symbol in SQL statement

    Summary: Using the multiplication operator (*) with SeletSql() causes an error. Steps to Reproduce: 1. Add the attached custom APS page (TESTmulti.asp) to a menu (e.g. the User menu). 2. Run it. It should display a list of quotes created by the current user. Expected result: The quotes displayed should...
  • Wiki Page: 492-16507 - How to: Restore the LeadCompanyScreen

    Summary: A customer may delete the Lead Company screen, and wish to restore it. Symptoms: Screens are hard-deleted when removed from CRM. There is no option for restoring screens within CRM when they are deleted. The screen will need to be restored directly on the database (if you have access to it)...
  • Wiki Page: 536-16923 - Select Search Advanced issue with 71G

    Steps to Reproduce: 1.Create a new person search select advance field (oppo_agent) and add it to the opportunity web picker screen. 2. Find an opportunity that's not associated with a Person & click "Change" 3. Click on New Person and enter in person details select Save & Continue...
  • Wiki Page: 492-17148 - Missing buttons for Translations and Component Manager

    Summary: Users may find that they have no rights to the Translations and Component Manager menus under Administration -> Customisation . Cause: These options are not available to Info Manager Users. They only are available to System Administrators.
  • Wiki Page: 636-17184 - Custom date fields changing date if included in a workflow rule in certain timezones

    Summary: Custom date fields are changing date if included in a workflow rule in certain timezones Symptoms: If a custom "date only" field is included in a workflow rule in certain timezones the date will change when the workflow action is pressed on a sample record. Status: This has been stated...
  • Wiki Page: 492-17065 - Setting an onload event may result in a CRM screen not rendering

    Summary: Adding an onload event via a Custom Content script may result in a CRM page remaining blank after loading. This is caused by the script replacing the onload events. Symptoms: A customer added a Custom Content script in the following format: <script> window.onload = function(){ alert("The...
  • Wiki Page: 492-16667 - How to: Creating a custom merge to Excel

    Summary: A customer had a requirement to merge data from Sage CRM to Excel. Currently, Sage CRM only supports mail merges to Word - they were wondering if this is possible with a custom ASP page. How to: There are a number of ways of generating XLS files from a classic ASP page. Here's a couple of...
  • Wiki Page: 536-17313 - HOWTO: Amending the size of the FCKEditor window and email field

    Summary: The customer had a couple of requests regarding making a larger area visible when creating and editing emails. Symptoms: 1: Can the size of the FCKEditor (Email Editor) be increased? Currently the IFRAME has a dimension of 698px wide and 250px in height. 2: When an email is filed in CRM, the...
  • Wiki Page: 492-17400 - Validation errors and hidden screens

    Summary: Validation errors may appear as a result of hiding required fields using a client-side script. More information: Depending on the field type and the validation that is causing the issue, the specific field that is causing the problem may not be referenced explicitly. A typical example of this...
  • Wiki Page: 632-17617 - SQL Error shown when creating a company after changing field type

    Summary: A user edits a custom "Search Select Advance (Adv Search Select)" field that was created under the company entity. The user changes this SSA field to a selection field. Symptoms: The user then trys to create a company using the updated field but the following error message is shown...
  • Wiki Page: 492-17872 - Adding an entity's ID to a group

    Summary: It is possible to edit the metadata for a primary entity's ID field so that it can be used in groups. However, the ID will not then appear in the group contents. Editing the field's metadata through SQL is not supported, though a number of other methods exist for displaying unique IDs...
  • Wiki Page: 492-16287 - Creating new view - 3900 character limit in non-IE browser

    Summary: Users may be unable to create views longer than 3900 characters in Sage CRM when using browsers other than Internet Explorer. Symptoms: The issue can be reproduced by attemptign to create a view with a length greater than 3900 characters. Here's an example: create view vLongView as select...