Browse By Tags

  • Wiki Page: 636-17151 - Some fields appear as if they are outside the screens they are supposed to be contained in.

    Summary: Some fields appear as if they are outside the screens they are supposed to be contained in. Symptoms: Fields that have 2 rows on a new line at the bottom of a screen will appear as if they are not in the screen. The fields look as if they are not inside the border of the screen: More information...
  • 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: 536-17314 - .NET API: Writing binary data to a CRM webpage

    Summary: A customer had a requirement to use the .NET API to write binary data to the outputstream. Their exact requirment was to use the .NET API to create a PDF file on the server, then embed the file in a CRM screen. the following shows a method for creating a PDF file in CRM's library, then embedding...
  • 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...
  • Blog Post: Cleansing data submitted by users in the COM API

    Securing web applications can be tricky. One surefire way securing the system is to lock it in a box, where no-one can switch it on, much less enter data into it. Unfortunately, this is not the making of a useful CRM system. In Sage CRM 2017 R2, we’ve added a new feature that should allow partners...