Posting G/L Accounts just became easier! (V2.10.00.128)

G/L Account Keys are usually defaulted from other tables, so we don't have to include them in a post Request. For example, posting an A/P Invoice will default the Vendor Account Key for the line detail. If you need to post a G/L Account, read further.

Posting G/L Accounts through the Business Object is made difficult because an Account Key is required. You can get the Account Key by making a SDE Request for the key and passing the Formatted Account number and specifying the Account index.

Starting with SDE Build 128, you can pass the Formatted Account as the Account Key and SDE will translate the Formatted Account to the Account Key for posting.

Easier Navigation from Windows Start Menu (v2.10.0.126)

Earlier versions of SDE required that certain functions be launched from inside the application. Starting in build 126, the Windows Start Menu includes the folder "SDE Sage 100 API", containing the following functions:

• SDE Application
• Web Configuration
• Web Start (Restart)
• Uninstall SDE

SDE Start (Restart) will shutdown all instances of the web connection and restart the Windows Service or application.

Return Tracking Numbers from History (v2.10.0.119)

The A/R Invoice History business object does not have a link to the package table which contains the tracking numbers. (The user interface has a button to access the business object.)

Our ARSDE_InvoiceHistoryInquiry_BUS, delivered with SDE, provides the link to the Tracking Numbers, or any other field in the AR_InvoiceHistoryTracking table.

SDE will return an array of Tracking Numbers if thats the only column requested. Otherwise an array of package information objects will be returned.

Of course, you can GET Tracking Numbers from the standard Sage object AR_InvoiceHistoryTracking_BUS, though it might be easier to get the Tracking Numbers with the invoice.

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.

Invoice History Header & Detail (v2.10.0.117)

The Sage 100 Invoice History business object does not have a detail object for the invoice lines. In order to return a complete invoice from Sage your application would need to make two requests.

SDE, the JSON and XML API for Sage 100, remedies the situation by delivering overrides to the header and detail objects to allow your application to retrieve the complete invoice with one request. These overides are not standard Sage overrides, but direct overrides of those two classes.

We've added the Invoice History Resource to the Demo page. The Response contains both header and detail columns. Note the Invoice Total is returned. Invoice Total is not in the table, but it is returned as an expression with an alias.

Offset and Limit Paging (v2.10.0.115)

SDE, the JSON and XML API for Sage 100, now handles offset-based paging using the offset and limit query parameters.

To fetch the first page of entries in a collection, the API needs to be called with the offset parameter set to 1 and the limit parameter set to the desired number of records to return. To fetch the next page of entries, the API needs to be called with an offset parameter equal to the sum of the previous offset and limit values. The limit parameter would stay the same.

To try offset-based paging, go to the API Demo page and check the Use Offset checkbox before hitting the Get All or Get w/Filter buttons.

Using HTTP Authentication (v2.10.0.114)

SDE, the JSON and XML API for Sage 100, now can take advantage of the HTTP Authentication Header.

The "Basic" HTTP authentication scheme is defined in RFC 7617, which transmits credentials as user ID/password pairs, encoded using base64.

To try the basic authentication, go to the API Demo page and check the Basic Authentication checkbox before hitting the Get All or Get w/Filter buttons.