API

Like for Sage 50cloud and Sage 200cloud, the API of Sage 200 Standard Online should also cater for Automatic Matching and Closing of Purchase Orders. A basic feature of any Sage complementary software that is not available in this version of Sage ...

Currently it is possible to get summary and statistical details of an invoice through the API endpoint sales_posted_transactions. However, I have a need to get the individual line items on the invoice as well. It appears that there is currently no...

You can import Product Groups, much like stock items, and they can be a complicated structure with all of the Search Categories, Batch/Serial settings and what not, but you cannot Export them. This is useful if you are moving Product Groups to oth...

I have a large amount of stock transactions to import, Adding to Stock or 'Writing off' as a result of stock taking. We cannot use the Stock taking facility because of it's limitations in not reading a retrospective date for the Stock level, just ...

When importing new Stock Items in to Sage 200, you cannot specify a BOM Item Type on the CSV file, e.g. BOM, Component, Phantom item or Built/Bought. Therefore, the newly imported Stock Items have to be amended manually once they're in Sage. This ...

Hi, Would it be possible to add the postal_name field to the Sop_orders_delivery_address endpointas a POST/PUT field. Sage 200 field PostalName in SopDocDelAddress. Thanks

This functionality exists in Sage 200 SDK(The same as in Sage 50), and our customers really would like to continue to use it in Sage 200 Standard. I'm sure it shouldn't be a big task because API is based on Sage200 SDK. We really need. Thank you, ...

The customer has over 2000 stock records, they are going through a major rebranding process and need to update all of their stock item descriptions to reflect this. As it stands they will have toupdate all of these manually. The &Import Stock ...

Ability to colour code items for when it prints out on invoice (stock, comment etc) without having to go into the set up.

There are major limitations to the functionality offered by the current Sage 200 Standard API. In particular there is no endpoint for creating an unposted invoice. This leave a major hole in any integration that depends on invoices being created