What is SDE?
Our Sage 100 API, SDE, works with JSON and XML to post your data to Sage 100 Standard, Advanced, and Premium. Web and Application developers use JSON or XML to post Sales Orders, Quotes, Customers, Vendors, and almost any object in Sage 100. Developers can also define the data returned by a GET or the response from a POST. SDE uses Sage 100 Business Objects to maintain data integrity.
How does SDE Work?
SDE resides on your server, listening for JSON or XML requests.
When a authorized request is received, SDE queries your Sage 100, and responds to the request.
Post requests (update and create) are handled by the Sage 100 native business objects.
Even User Defined Tables and Fields can be read, and written to, via SDE.
Business Objects and object overrides, written by Sage 100 Developers, are available as well.
Who uses SDE?
We have many customers running SDE. Listed below are a few. We don't provide company names, but it may be helpful to know about the connections that are possible with the Sage 100 API. If you are intereseted, please contact us through the Support page.
|
SDE connection to Woo Commerce A Georgia customer produces and sells trade show and event equipment. Their products run the gamut on all things exhibition related.They already had a Woo Commerce web store, but wanted a way to post the orders from the site directly into Sage 100. Working with their development staff, Woo Commerce now posts a JSON order document to SDE, which posts the order into Sage 100. |
|
 | ||
|
SDE connection to Zoho An Oklahoma customer manufactures quality drywall materials, tools and supplies. They are integrating Zoho with SDE to pass Sales Orders directly through to Sage 100. |
|
| ||
|
Paya developer posts CC to Sales Orders Another customer created their own custom web store that posts paid Sales Orders into Sage 100 through SDE.The creators of the web store are Paya developers. The site charges the customers credit card online. When the order is posted to Sage 100, they include all the Paya transaction information. |
|
| ||
|
Coupa posts cXML to SDE SDE is running at national printing company that wanted to move off their EDI platform onto a new system managed by Coupa using cXML. Their national customer has close to a thousand stores all ordering automatically through Coupa, posting orders into Sage 100.With the success of receiveing orders through Coupa, they've added another connection for a printer supplies company to post their orders. |
|
| ||
|
SDE interfaced with SalesForce A netting manufacturer created a button in Salesforce that posts CPQ quotes to Sage 100 through SDE. |
|
| ||
|
Developer pulls data for remote reporting A fireplace distributor in New York is working with SDE to pull data out quickly for custom reporting. |
|
| ||
What's New?
Faster Returns with Indexing (v2.10.0.118)
SDE, the JSON and XML API for Sage 100, now allows the selection of the best Sage Index for your query.
The A/R Invoice History tables can grow very large. You can page results,
setting a customer filter, but since the primary index is by invoice number,
the search reads every record.
If the request contains customer index along with that filter,
the query will only see the records with that customer,
and return the page much quicker.
We've setup an index option on the Demo page.
The ABC Demo Data doesn't have any large tables, but you will see the index syntax.
Use the Products or Invoice History Resources.