Browse By Tags

  • Blog Post: Discovering Data Relationships in Code

    You may have a business requirement to cascade a change through the child records of a company. I have discussed previously how a table level script can be used to update all opportunities if the company is reassigned to a new account manager. See the article " A Table Level Script to update Opportunities...
  • Blog Post: Integration with External Systems and the Synchronization of Application Data

    Introduction Sage CRM is integration-ready straight out of the box. It can integrate quickly with Sage BMS products, as well as other external applications through secure, standards-based web services and APIs. In this article I want to discuss the different approaches that can be taken by a developer...
  • Blog Post: Adding a Button that Passes Contextual Information to an External Webpage

    You can add a button In a custom ASP page In a the code of a .NET assembly In a an existing system screen Buttons in an ASP Page If this is in an ASP page then the code for a simple button to call an external ASP page looks like var strCallASPButton = CRM.Button("ASP"...
  • Blog Post: Building a Simple Quick Search Page

    Entities such as Case and Solution use a reference field as an alternative key. This is the 'ticket' number (case_referenceid, soln_referenceid) that is used as a public and convienent way of identifying each record. In the default demo system the fields case_referenceid and soln_referenceid...
  • Blog Post: Checking Versions in Sage CRM

    How can we tell what version has been installed? The patch and version of the software is announced on the Logon Screen. Again within the product you can check the version by going to My CRM> Preferences and clicking the About CRM button. The version can be checked programmatically. This becomes very...
  • Blog Post: The Sage CRM .NET API

    The diagram below shows the general architecture of Sage CRM. Here you can see very clearly that the .NET API is an alternative and NOT a replacement for the COM API which is currently used to build application extensions with ASP pages. Both the .NET API and the COM ASP API use the Meta...
  • Blog Post: Resetting Passwords

    I have had a few emails from different people over the last few weeks asking about code that will allow a system administrator to quickly reset a users password. I created a little ASP page that demonstrates how this can be done. You can develop this idea further by send an email to the user. The...
  • Blog Post: Working with a Stored Procedure that returns a result set.

    I have discussed calling Stored Procedures from within Sage CRM before in the the article " Using the COM CRM.CreateQueryObj() to call a Stored Procedure ". From that article it can be seen that it is possible to call stored procedures where ever a QueryObject can be instantiated. This could...
  • Blog Post: Some thoughts on Importing Data

    I have written several articles in the past about the importation of data into Sage CRM. This article then is a 'header' record that attempts to bring these different thoughts together. It is certainly not unusual for a partner to occasionally need to design a custom import mechanism into...
  • Blog Post: Creating a PipeLineGraphic in an application extension using COM API ASP

    I have discussed in a previous article how customization can be carried out on a PipeLineGraphic chart used in a system built page, for example on the Opportunity List page in the My CRM tab area. The PipeLineGraphic block is available within the COM and .NET APIs but it has not always been straight...
  • Blog Post: Redirecting from a COM ASP page to a .NET assembly

    You may have a need to redirect from a custom page written using the COM ASP API to a .NET assembly. I have written about redirecting from COM ASP page before in the article " Redirecting to an ASPX (ASP .NET) Page from a Classic COM ASP page " The code below shows how a URL for the redirect...
  • Blog Post: The relationship between the SOAP Web Services and the other APIs

    A customer asked me whether the SOAP Web Services were an extension of the .Net API or a separate API built on top of the COM API. Below is a diagram that is frequently used to explain the Sage CRM Architecture. This diagram represents the hybrid architecture of Sage CRM pretty well. It shows...
  • Blog Post: An approach to recording completed marketing communications sent by an external system

    A customer uses an external system to generate marketing emails to contacts. These contacts exist as records in their accounting system that is integrated with Sage CRM. This means that the contact exists in both Sage CRM and the Sage BMS but because the emails are sent from a third party system integrated...