Browse By Tags

  • Wiki Page: 536-17430 - Right click menu items does not work for custom entity

    Summary: When creating a main menu item for a custom entity you must make sure the tab group caption matches the entity name. Symptoms: If the tab group caption is different to the entity name then the right click context menu will not work on that menu item. Solution: Make sure the caption is the same...
  • Wiki Page: 492-17442 - .NET API: File not found error when using .NET 4.5

    Summary: Attempting to run a .NET DLL built using the Sage CRM .NET API and .NET 4.5 may result in an error being thrown in Sage CRM. Symptoms: The following error will be displayed: File not found: C:\Program Files (x86)\Sage\CRM\CRM\CustomDotNet\MyDLL.dll An error has occurred in a CRM .net customisation...
  • Blog Post: Customizing campaigns and marketing features

    Sage CRM out of the box provides users with a very useful set of marketing or campaign management features. Users need to have 'Info Manager' rights in order to be able to use the campaign features. The campaigns area is accessed from the main menu. In the image above you can see...
  • Blog Post: Graphical Workflow for Marketing

    In a previous article " Customizing campaigns and marketing features " I discussed how amongst the powerful features that Sage CRM provides are marketing automation functions which offer the ability to control campaigns, waves (phases) and wave items( activities). Running a campaign can...
  • Wiki Page: 492-17466 - Issue processing payload using crm.sdata function

    Summary: An attempt to use the crm.sdata function in the Client-Side API may fail when the user's browser is Internet Explorer. Internet Explorer's JavaScript engine will report an issue reading the payload returned from the SDATA request. Symptoms: The following script error may be displayed...
  • 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-17451 - Metadata not updated when editing ProductFamilyGrid

    Summary: Changes made when editing the Product Family Grid (such as the adding of sort options to field) may not be applied when the grid is saved. Symptoms: ProductFamilyGrid can be edited under My Profile -> A dministration -> Customisation -> Product Families -> Lists . On saving changes...
  • 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: 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...
  • Wiki Page: 492-16997 - Screen formatting errors may occur when calling RunBlock

    Summary: In v7.2, blocks called using the RunBlock method may display with "glitches" on-screen. Symptoms: There are two formatting issues visible. 1: There is padding missing between the edge of the block content and the side of the EWARE_MID div. This is caused by a missing TD with a blank...
  • Wiki Page: 536-17627 - Scroll bar missing in IE in custom entity summary screen

    Summary: When opening a custom ASP page, the page does not load fully and when the page is resized, the vertical scroll bar is missing. Resolution: In one particular instance there was a malfunctioning custom content script on the screen the customer was navigating to. This script was referencing a field...
  • Wiki Page: 536-17539 - How can a secondary entity be converted to a primary in 7.2?

    Summary: A user has asked if there is a way to convert a secondary entity into a primary entity. Resolution: To make an Entity appear as a Primary Entity The entities that are shown as Primary Entities in the Administration -> Customisation screen have the field bord_primarytable set to 'Y'...
  • Wiki Page: 632-17358 - Runblock in AdminUsers menu is not displaying

    Summary: When adding a new runblock (CompanySearchBox) to the AdminUsers Menu ( Administration -> Advanced Customisation -> System Menus -> AdminUsers ) and then going into the Administration -> Users and clicking on this new option a blank screen is shown. The new block is not displayed...
  • Wiki Page: 536-17681 - .Net API FindRecord method changes the encoding #7754314

    Summary: The .net API method FindRecord changes the encoding of the where clause in the SQL statement that's run on the database. If the where clause contains special characters like the German umlaut (Ü) then the method wont find anything. Record CompanyRecord = FindRecord("Company"...
  • Wiki Page: 632-17531 - Required field in Document entity was ignored

    Summary: Create a new field in the secondary entity "Document", add the new field to the "Library Web Picker" Screen and make this a required field. Add a new document using the "Add file" option under the documents tab within a company. Save this document without inputting...
  • Wiki Page: 492-17823 - How to: Integrating Sage CRM with a web-based SMS provider

    Summary: Out of the box, Sage CRM only supports SMS messaging via an SMTP gateway. SMS providers typically support a range of protocols for interacting with their services. These might include SMTP, SMPP, FTP, and RESTful web services APIs. This article exists as a demonstration of how to integrate Sage...
  • Wiki Page: 632-17617 - SQL Error shown when creating a company after changing field type

    Summary: A user edits a custom "Search Select Advance (Adv Search Select)" field that was created under the company entity. The user changes this SSA field to a selection field. Symptoms: The user then trys to create a company using the updated field but the following error message is shown...
  • Wiki Page: 632-17629 - Full field name not displayed in report content

    Summary: A user creates a field with a caption with 25 characters or more, for example in this case comp_superdupercompanyfield. When trying to add this field to a report the user cannot see the full name of this field: Cause: The cause of this issue is that the report "Select Column" window...
  • Wiki Page: 492-17871 - Unexpected event after adding field on secondary entity

    Summary: An issue may arise when a custom field is added to a Progress entity, and that same field is added to a summary screen in Sage CRM. Fields added to Progress tables need to also be added ("mirrored") to the parent entity. Symptoms: Consider the following example: An administrator adds...
  • Wiki Page: 492-17872 - Adding an entity's ID to a group

    Summary: It is possible to edit the metadata for a primary entity's ID field so that it can be used in groups. However, the ID will not then appear in the group contents. Editing the field's metadata through SQL is not supported, though a number of other methods exist for displaying unique IDs...
  • 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-16287 - Creating new view - 3900 character limit in non-IE browser

    Summary: Users may be unable to create views longer than 3900 characters in Sage CRM when using browsers other than Internet Explorer. Symptoms: The issue can be reproduced by attemptign to create a view with a length greater than 3900 characters. Here's an example: create view vLongView as select...
  • 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...