This release is scheduled to go live beginning on the evening of February 21, 2020.
Inventory Control
Linked inventory adjustments
You can now create inventory value-only adjustments for specific source transaction lines. For example, after paying for a purchase, you might need to adjust the value for items in the vendor invoice. For FIFO and LIFO costing, value-only inventory adjustments require a transaction line, otherwise it’s optional.
To create a value-only inventory adjustment, create a new inventory transaction and provide the source transaction line you want to adjust. Only purchasing and inventory control transactions with a Value-only inventory effect can be adjusted.
For more information, see the adjdocentrykey parameter on the following:
Purchasing
Purchasing transaction allocations
You can now use transaction allocations to automatically distribute amounts for non-Inventory Purchasing transaction lines across multiple dimensions, such as departments, locations, projects, or classes. After receiving an invoice from the vendor, you can allocate the expense directly on the purchase invoice—no need to switch to AP to do the allocation.
Currently, this feature applies to only those purchasing transactions that post to the Accounts Payable subledger.
For more information, see the allocationid parameter on the following:
You can also create transaction definitions that support these line-level allocations. See the ALLOW_ALLOCATIONS parameter on the following:
Contracts
Draft contract state
You can now save a contract, contract line, or expense line as a draft without affecting the GL or the Contracts subledger. When your data is ready, you or someone else can come back and post the contract, contract line, or expense.
For information about creating these objects as drafts, see the STATE parameter on these functions:
To post draft versions of these objects, see:
Web Services
New query function
A new query function that provides significant enhancements over the existing readByQuery function is available.
You use the query function to return a list of objects that match a given condition, just as you would with readByQuery function. However, query supports more robust, complex query statements using an XML-based syntax with defined rules and error checking. The new query provides more operators, lets you sort results, perform aggregate operations such as sum or average, use a larger page size limit, and more.
Finally, with the new query, you can get the values for fields on related objects and/or use them in filters.
For example, the following lists bills where the related vendor’s credit limit is greater than 50,000. Note the use of the dot operator (.) to access the related field.
<query>
<object>APBILL</object>
<filter>
<greaterthan>
<field>VENDOR.CREDITLIMIT</field>
<value>50000</value>
</greaterthan>
</filter>
<select>
<field>RECORDNO</field>
<field>VENDORNAME</field>
<field>VENDOR.CREDITLIMIT</field>
</select>
</query>For more information:
Note: Custom objects are not currently supported.
Platform Services
Learn how to create a custom application with the new Platform Application Tutorial. This tutorial walks you through the steps of building and publishing a sample application. You will create custom objects, relationships, pages, triggers, API calls, and more!