Chances are, if you work or use SalesLogix (or any Sage product) you've heard of SData by now. SData is a basically a web enabled API for SalesLogix allowing you to interact with SalesLogix data from an external application or website. The great thing about SData is that it is a specification that is implemented via RESTful web services. This means you're not limited to using SData with a particular technology (such as exclusively via .NET). In a nutshell, SData works via sending and receiving XML payloads via a URL. Pretty simple. This article will take a high-level overview of SData as an introduction (which means there will be several more in-depth posts on the way).
In my previous post, an Overview of SData, I outlined the working parts and anatomy of the web enabled API for SalesLogix known as SData. In this post I will show you how to take your first step with how to get the SData Client Library.
If you followed my last two posts, you'll know some basics of what SData is and how to get it to use in your projects. In this post, we will take this a step further and look at how to actually use it, starting with how to query data from SalesLogix.
When you're developing an application or customization using SData for SalesLogix, the fewer trips you make to the server the better. Moving data back and forth across the wire will always be the biggest bottleneck in your code, so making use of nested payloads will save you some trips by bringing all the data you're after back in one pass.