View more results: All Community | Partner Community
  • Blog Post: Creating a New Entity using COM API ASP

    This article has been updated to allow download from this site. I have written before many times about creating ASP pages to support access to a custom entity. How does Meta Data create a Screen? DPP and Standard include files for ASP pages The Basic Structure of an Edit Page How...
  • Blog Post: About the Development Partner Program

    I look after the education of Development Partners (DPs) and so I am very involved in the Development Partner Program (DPP). The Sage CRM DPP is designed to support partners who are creating add ons and extensions to the Sage CRM product. Sage certainly expects DPs to create extensions to Sage CRM. But...
  • Blog Post: Adding Derived Fields in Views into Meta Data

    I originally wrote about creating derived fields in a view in the article " Custom_Edits and Derived Fields Created in Views ". This discussion is a continuation of the ideas expressed in that article and will show how meta data definitions of a calculated field can be easily added into Meta...
  • Blog Post: Where am I?

    When working with CRM you may have a requirement to know the servername and install names with which you are working. System Options There are a few nice techniques that we can use in ASP pages. For example the COM API has a method that allows us to check the contents of the custom_sysparams...
  • Blog Post: Making the Best Use of a component Parameter Screen

    If you have created a set of customizations for Sage CRM the probably you do not want to spoil the users experience by presenting an empty parameter screen when a System Administrator comes to install the product. For example the System Administrator may start to install a component: And then...
  • Blog Post: Using Logos and images in Component (es and ecf) Files

    It is very easy to include a company logo in the es component script file For example: AddMessage('<img src= http://localhost/CRM/img/Icons/Admin.gif >;'); But the Component Parameter file (ecf) causes us a problem. Most < > tags are converted into &lt; &gt; symbols and so...
  • Blog Post: Searching for a Person by Business Address. An example of codeless customization.

    A customer had a business requirement to be able to search for people and filtering them by either their business or home address. When an address is entered into the system for a person a user can specify the type of address as can be seen in the screen below: The default choice for address...
  • Blog Post: Component Recording

    When working with the Component Manager it is possible to record customizations that you make and input to another CRM system. This is an extemely handy feature saving lots of time , effort and possible tantrums. Recording a component is very straighforward. I will walk you through the few short steps...
  • Blog Post: Documentation and Resources for the Component Manager

    Question Topics seem to rise and fall like hemlines in fashion. I might not get asked anything about a topic for a month and then suddenly the world and his wife are demanding help on say 'buttons'. Just recently there have been a spate of questions about Reporting and the Component Manager....
  • Blog Post: Cloning an Opportunity using the ASP COM API

    I have written earlier about cloning or copying existing records. Please see the article Using the COM API to Clone a Record . This article provides a worked example on how you can use that article to add a button to the opportunity summary screen that will copy an existing opportunity record and...
  • Blog Post: Customizations and components for systems that lack an extensibility (Enterprise Integration Server) license

    You can see in the image below that I am using a system with both a license that contains both Enterprise Integration Server and Developer rights. Either of these rights would allow me to create a component containing metadata changes and files that could be delivered into a target system...
  • Blog Post: Sage CRM and Referential Integrity

    One of the great strengths of Sage CRM is its openness. Its data model is documented and published and available to members of the Developer Program. In some applications relationships between the different entities may be fixed or defined within the database. This is not the case within Sage CRM...
  • Blog Post: Sage CRM 2017: Company Workflow Example

    You can define a workflow for the Company entity. Creating a company workflows is different from creating a new workflow for the opportunity or case entity. The entities, Leads, Cases, Opportunities and Solutions all work in a similar way. They have a progress table associated with them and they assume...
  • Blog Post: Some thoughts about removing a component.

    I didn't intend to write this as an article. Like many of my posts it was simply going to be an answer to a question in the forums but when it grew in length I decided it would work better as an article. But I must stress that these are only my initial thoughts so I would expect that partner experts...
  • Blog Post: Moving Files Using the Component Manager

    The component manager allows us to deliver not only Meta Data changes to a system but to also drop in and manage files like new logos, icons, and ASP files. This article will cover the methods CopyASPTo() CreateNewDir(); CopyASPTo() Syntax: CopyAspTo(SourceFileName As String, TargetFileName...
  • Blog Post: Scripting Escalation Rules in a Component

    I found this a very interesting issue. If you have created an escalation rule outside a workflow you will not be able to find a place where the component manager script can be generated. So how or where can you get the script of an escalation rule that was created outside a workflow? If an escalation...
  • Blog Post: Suppressing Display of Duplicate Meeting Records in Company and Person Context

    A component that implements this feature can be found in the download folder " Example components and developer resources ". You will need to be logged on to the community with the correct rights to be able to access this library of resources. The image below shows the default behaviour...