Browse By Tags

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...

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...

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...

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...

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...