• Wiki Page: 492-17874 - Case_OpenedBy metadata may prevent field from operating as expected on-screen

    Summary: A metadata issue exists within the Case_OpenedBy field in a standard Sage CRM install. This issue can be resolved via a SQL script. Symptoms: When Case_OpenedBy is added to a screen (such as CaseDetailBox), it may not be displayed correctly. The field will display, but some components (such...
  • Wiki Page: 492-17957 - Sage CRM system lock - unable to log back in

    Summary: A customer may lock Sage CRM for customisation using the option available under Administration | System | Lock System . If they encounter difficulties with the password of the user who created the lock, they may be unable to log back into Sage CRM. More information: Running the following SQL...
  • Wiki Page: 492-17962 - Changing User Select display format

    Summary: User Select fields in Sage CRM can be displayes in one of two ways within Sage CRM. Which format is used depends on an entry on the CustomSysparams table named DropdownThreshold. More information: When linking a Sage CRM entity record to a user, a particuklar type of field is used. This field...
  • Wiki Page: 492-17966 - Character limit when editing customisation fields

    Summary: Certain textarea fields responsible for customisation input may have a MaxLength property applied to them when Internet Explorer is used. The database columns backing these fields typically use an nvarchar(max), so users are preventing from entering valid input into these fields. Symptoms: On...
  • Wiki Page: 492-17967 - Web to Lead: Lead_Opened field

    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...
  • Wiki Page: 492-17968 - Custom content for Custom Entities

    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...
  • Wiki Page: 492-18022 - How to: Adding thousand separators to numeric fields

    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...
  • Wiki Page: 492-18073 - Translated button IDs

    Summary: Up until Sage CRM 7.3 SP3, a number of button IDs within the product were localised. This had the effect of different HTML ID attribute values being returned depending on which user language was selected. In the 7.3 SP3 release, a large proportion of these IDs have been identified and fixed...
  • Wiki Page: 710-18116 - Smart Entity - unable to edit or add list like with a standard entity

    Summary: Once you have built a selection list on a Smart Entity you are unable to edit or add to this list like you would with a standard entity Resolution: In Administration -> Customisation -> Translations enter one of the values that already exist in your list into the UK translation box Select...
  • Wiki Page: 720-18137 - Adding an ASP Page to Company Tabs

    Summary: Adding an ASP Page to Company Tabs Steps to add ASP Page: 1. Create an ASP Page and add to the directory:  The default location For 32-bit (x86) system is C:\ProgramFiles\CRM\...  And for 64-bit (x64) system is C:\ProgramFiles(x86)\CRM\... 2. Log on to Sage CRM as Admin 3. Go to My Profile >...
  • Wiki Page: 720-18139 - Adding a block to the Interactive Dashboard using an ASP page

    Summary: Adding a block to the Interactive Dashboard using an ASP page Steps to add Content Block: As we can see in our previous article 720-18137 , We have added an ASP page in company Tab. Now in this article, we will add a content block using that ASP Page. 1. Log on to Sage CRM as Admin Go To My...
  • Wiki Page: 720-18211 - CTI Integration with Customized Format that supports RFC4967

    Summary: CTI Integration with Customized Format that supports RFC4967 Description: A mechanism to express a dial string in a 'sip:' or 'sips:' URI is required. To know more about RFC 4967, Please refer this link: http://www.networksorcery.com/enp/rfc/rfc4967.txt You can customise your...