Browse By Tags

  • Wiki Page: 608-16540 - Howto: Add a searchable custom field in SageCRM

    Summary: While Sage CRM has a large number of useful fields against Companies, People, etc, what's available may not exactly suit your needs. This article describes how you can add your own custom, searchable field to Sage CRM. More information: Creating a custom field for the company entity To add...
  • Wiki Page: 636-16939 - HOWTO: Set the Territory as a Required Field or default it to the user's territory

    Summary: This KB article will show you how to make sure that new companies have a territory and that it can not be set as default Resolution: 1. Go into Administration -> Customisation -> Company -> Screens -> Company Summary Screen 2. Click on Company: Territory (comp_secterr) 3. To make...
  • Wiki Page: 593-16278 - How to: Adding a 'last note' column to the Company Grid

    Summary: A customer may have a requirement to add a date/time column to the Company Find grid depicting the last Note record was created against a company. This can be done by creating a new view, and amending an existing view. More information: This customisation can be carried out by doing the following...
  • Wiki Page: 536-16734 - 7.2 ASP page issues (multiple menus)

    Summary: A number of issues have been identified with relation to ASP pages since the frameset removal. Most of these problems stem from the fact that the ASP page is now rendering in an IFrame instead of the old EWARE_MID frame. An action 6030 was created for linking to ASP pages which caused a render...
  • Wiki Page: 536-16782 - Default behaviour of the Email Manager JavaScript files

    Summary: A number of support cases have been raised regarding the expected functionality that is in the default Email Manager scripts. The article will seek to clarify what functions are available in each script, and when they should be used. More information: Two default scripts are available for the...
  • Wiki Page: 492-17545 - Tool: URL Compare - translating Sage CRM URL key values

    Summary: Sage CRM uses URL keys to define the system context. By this we mean the main entity type, as well as the individual entity record, and any secondary entity records that are currently being accessed by a user. A full description of how this works within the product is available here . Developers...
  • Wiki Page: 492-16248 - HOWTO: Changing notification styles (v7.1 and earlier)

    Summary: A customer may have a requirement to make notifications in CRM stand out more from the rest of the items onscreen. It was found through testing that users were ignoring notifications, as they weren't obvious enough on-screen. Symptoms: This can easily be customised using CSS. You can view...
  • Wiki Page: 536-17324 - Problem saving location on maps component

    Summary: On one of our on-premise installs we had this behaviour with maps component. We can change the map location but it saves an address which is tens of kilometres on the south west of the address saved. Solution: When I view the HTML source of the maps page, I can see the script below. As you can...
  • Wiki Page: 492-17781 - Installation of language packs on earlier versions

    Summary: A number of language packs are provided by Sage for use with Sage CRM. These language packs are provided for specific versions of Sage CRM, such as 7.1f. A query may arise where a customer wishes to apply a language pack for an earlier version of Sage CRM. In these instances, language packs...
  • Wiki Page: 492-17910 - INFO: Actions that trigger metadata refreshes in Sage CRM

    Summary: A customer may query which system actions in Sage CRM cause the system metadata to be updated. This is not an exhaustive list, but covers the majority of actiosn that can trigger refreshes. More information: A metadata refresh is carried out when the following system actions are carried out...