Browse By Tags

The SData 1.1 Standard provides a comprehensive query language. Sage CRM allows the use of SData within SData gadgets where feeds from external Sage applications can be consumed. It also provides read only SData feeds that allows data from Sage CRM tables and views to be accessed. The SData query language...

This article is the first of a new series of articles that will provide you with a jump start on developing with the new RESTful API for Sage CRM. Not everyone reading this will be familiar with SData and so I need to start from the beginning and explain what SData is and how it works. I am not going...

In this article I want to consider Sage CRM's Architecture, its development options and the importance that this places on the use of Web Services especially REST and SData for integration. We need to consider what is available to use now and look and what has been publicised and documented. We...

In this article I want to start looking at the SData in action and start to understand what the RESTful API offers. And if we are going to work with SData then we need to have an instance of Sage CRM with which we can play. Here we need to work with an instance of Sage CRM 2017 onwards. I want...

In this article I want to consider the way in which the RESTful API allows system administrator to easily extend the reach of the API's access to data across custom entities and views with SData. It is very useful being able to retrieve data using end points like these, http://[servername...

In this article I want to think about security. This is both the security that governs the rights of access to the system and the access that is then granted to a user accpording to the policies implemented within Sage CRM. One of the first things to note about the difference between the classic SOAP...

The classic SOAP web services provide us with an existing set of abilities to create, read, update and delete data. In this article I want to examine those web services in order to explain some of the limitations of the interface and why we can instead expect enhancement of the SData based RESTful API...

The SData standard has always been about enabling all types of Sage applications, whether they are desktop, server, or web-based systems to communicate with each other easily. The standard provides the basis of the RESTful APIs that can be used by our own programs, third-party applications and web sites...

I said in my last article that SData 2.0 can not be considered a 'green field' solution because SData has been already used through out Sage CRM right from the start of the move to the new Java based architecture. The desire for compatibility between SData 1.1 and SData 2.0 and what it may...

We have seen previously in this series that we can make a request directed at an instance of Sage CRM using SData 2.0 to fetch some data from an entity. http://localhost/sdata/crmj/sagecrm2/-/company('28') The result received when we use SData 2.0 is in JSON format. JSON stands...

In this article I want to look at three different examples of how we can use the SData 2.0 based RESTful API within Sage CRM to carry out CRUD actions. Post (Insert) a new record into a system entity Post an Entry and link to an existing entity. Post an Update to an Entry Post (Insert...

In this article I want to think how the ReadOnly SData provider can be used to extend the capabilities of Sage CRM. To do this I need to put the SData interface into some context. SData is a form of web service and as I discussed in the article " An Introduction to using the SOAP Web Services...