Browse By Tags

  • Wiki Page: 492-17147 - How to: Querying records using a Where clause in the client-side API

    Summary: It is possible to make SDATA requests using the client-side API. Some confusion may exist regarding the querying of records using a Where clause, as this function will always return a set of record objects. More information: In the following examples, we're using a Car entity, which has...
  • Wiki Page: 536-17173 - Missing vertical scrollbar in custom ASP page

    Summary: On a custom ASP page that contained an iframe there were issues with the scrollbars on the iframe because of the javascript in the asp page was attached to the window.onload event. Cause: For example if you bind to the onLoad event using javascript: window.onload = function() { doLoad(); } It...
  • 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-17471 - Frameset removal: duplicate element IDs in top content and EWARE_MID

    Summary: Fields added to the Top Content area in Sage CRM do not have different HTML IDs to fields added to regular Sage CRM screens. This may cause an issue if attempting to reference a screen element by ID. Symptoms: An example of the issue can be seen where comp_name field is added to both CompanyTopContent...
  • Wiki Page: 492-17512 - How to: Running performance tests on custom client-side scripts

    Summary: Those implementing Sage CRM may encounter issues around the performance of client-side JavaScript. These issues may be difficult to troubleshoot; while all major browsers include JavaScript profiling tools as part of their development tools, these may provide more information than is useful...
  • 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...