This release is scheduled to go live on the evening of August 18, 2017 Pacific Time.
This release brings the new AP workbench, only available in Sage Intacct Action, the new user interface. Accompanying the workbench is the new AP Payment object,
APPYMT. The API functions for
APPYMT let you apply line level credits and discounts for payments, which you cannot do with the existing payment functions. Each credit or discount is stored in an
APPYMTDETAIL object owned by the
APPYMT object. You can update a payment to add or delete
APPYMTDETAIL instances, and you can update the
APPYMT object itself, such as by changing the state from draft to posted, changing the bank, and so forth. See the API reference and entity relationship diagram for more information.
APPYMT object corresponds with the new Accounts Payable > Pay bills functionality in the Sage Intacct UI, not to be confused with the existing Accounts Payable > Select Bills to Pay functionality.
get_trialbalance API functions now support the dimension and reporting book filters already available when running account balance and trial balance reports from the user interface. The response data for these functions also includes the reporting book and currency as well.
Before these filters were available, integration partners had to use the
readByQuery API function on the
GLACCOUNTBALANCE object for getting comparable information. Because
GLACCOUNTBALANCE is the lowest level detail in the system (limited to budgetable periods), such queries might produce hundreds of thousands of records, making it difficult to get basic balances. With the new filters, you can easily get a trial balance for your consolidation book, or look up that one project’s expense account balance on a certain date.
Make sure to check out the Account Balances and Trial Balances API reference pages.
You can now move inventory from one warehouse to another in a single transaction with the Warehouse Transfer object,
ICTRANSFER. Before this release, you had to manually create both a transfer-out transaction and a transfer-in using
create_ictransaction. Check out the API reference for more information.
getAuditTrail API function used to require that you set the record’s unique name in the
objectKey field, which was problematic because record names take different approaches in objects across the system. You can now provide the record number in the
recordNo field instead. Check out the API reference for more information.
Previously, the update functions incorrectly allowed you to change the document number on Order Entry, Purchasing, and Inventory transactions. This is no longer allowed.
SUPDOCID merge field that identifies attachments can now be used in Smart Events and Smart Rules on the following objects:
Version 2 of the Sage Intacct SDK for PHP is now available. Make sure you check out the updated overview and guides that accompany this.
This release is scheduled to go live on the evening of May 19, 2017 Pacific Time.
Do you like the Web Services test tool? If so, you will love Postman. If you aren’t familiar, Postman is a popular API test tool that lets you send HTTP requests to a server and review the responses. Sage Intacct is now providing a Postman collection that you can modify and use to make your XML API calls. You can import this collection into Postman, then easily configure Postman with environments for your Sage Intacct companies.
See Your First XML API Calls to get started.
Note: Google is ending support for Chrome packaged apps, such as the Sage Intacct test tool, which is a good reason to try out Postman now.
A developer preview of the Sage Intacct SDK for .NET is now available. You can interact with the Web Services gateway using C# objects—you no longer need to work directly with the underlying XML API.
You can easily get started with the SDK, then follow up with the SDK Reference documentation.
Smart rules and smart events are now supported for roles and user groups in the Sage Intacct UI.
API documentation for contracts and revenue management is now available.
Notable features related to schema changes are highlighted below.
A new getAuditTrail function lets you list the audit trail logs for standard objects.
The following read-only fields are now available on Order Entry transactions:
| ||User ID for the user that executed the delivery.|
| ||Timestamp for the last time the document was delivered (printed or emailed).|
| ||Record number for the user that executed the delivery.|
In both AP and AR, the
EXCH_RATE_TYPE_ID fields on currency transactions for the same currency will now be nulled out (they are not relevant anyway).
You can now specify the source line key of an existing Purchasing transaction from which to convert. Specifically,
sourcelinekey was added to the
potransitem used by the
If you are reading this, you are experiencing the new and improved Sage Intacct Developer website!
While the developer.intacct.com URL remains the same, the content and the experience are new. The site provides more tutorials, new user guides, enhanced API documentation, code samples, SDK documentation, and more!
For starters, check out some of the new content on the site:
Do you have anything to say about the new site? Feel free to give us your suggestions.