Browse By Tags

The two APIs that I wish to consider in this article are mature, well developed and stable. They've been in the product for a very long time. Nevertheless, they are still used and still very much a useful pair of development options. In fact, they both play a very important part in integration and...

This article follows on from an earlier article " Combining CRM WebServices and ASP.NET ". That article had discussed using the SOAP based webservices of Sage CRM within an ASP.NET page. I had mentioned that such ASPX pages can be called from Sage CRM tabs (and by extension Button Groups...

One of the challenges that a developer will face when working with Self Service or with an external Application using the SOAP Web Services interface is that workflow is not fully covered by the APIs. Self Service and Workflow Self Service uses the COM API and is designed for use in ASP pages....

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

Imagine you need to retrieve information from CRM via the webservices interface; this query should combine data from multiple tables. In the COM API (ASP pages, self service, table level scripts etc) you could use the QueryObject to build the exact SQL you need. var mySQL = "SELECT Person.*,...

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

This is the first article in a series that will discuss creating a new database connection to the Sage X3 database using the standard Sage CRM features. The articles will take you through the steps so that you can understand how you can add new screens and grids to Sage CRM that will allow the listing...

This is the fifth article in a series that discusses creating a new database connection to the Sage X3 database using the standard Sage CRM features. Views that are intended to be used to list data from Sage X3 need to share a common key with the corresponding data in Sage CRM. We used as an example...

This is the sixth article in a series that discusses creating a new database connection to the Sage X3 database using the standard Sage CRM features. Fields that exist in the linked view in Sage X3 are mapped automatically to the Sage CRM Entry Types based on their physical database type but actually...

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

This article has been written for partners who need to be able to call Sage CRM screens in the context of external applications. This is not such a strange idea as there are several partners who have created add-ons to MS Office or to other desktop products that need to reference screens and data from...