Version 1.674 - 1.678

 Release Dates: April 29th – May 25th, 2015

Bug fixes:

1. For some users who packed sales orders from one location to another location in the system (this is not usual, as other users pack sales orders from one location to out of the system), it created multiple inventory details records for one single Lot. [Resolved in 1.674.]
2. When “Use qty 6 decimal places” was turned on, subtraction in Inventory Adjustment was giving inaccurate inventory results, due to the Qty on Hand field on the movement lines were only 2 decimal place. [Resolved in 1.674.]
3. After users changed the sales order header currency, the existing Sales Order line exchange rate didn’t get updated automatically. As a result, the sales order line price could not be converted to the correct currency automatically. [Resolved in 1.675.]
4. Count lines created movement lines with incorrect “Transfer Quantity”, due to the “Quantity in Inventory” was not set properly. [Resolved in 1.675.]
5. Trade agreements could not be applied to sales order lines properly, when sales order lines were entered by interfaces other than Ascent sales order lines visualforce page AND when using multiple currencies. [Resolved in 1.675.]
6. For FinancialForce users, when they used the “FFPackSO” button to pack a sales order, the Ascent invoice (“SI-XXXXXX”) was auto-generated, at the same time the FinancialForce invoice (“SIN-XXXXXX”) was generated. To avoid confusions, we removed the codes to generate Ascent invoice, when FinancialForce is on board. [Resolved in 1.676.]
7. When users added a credit memo line by using the standard "New Credit Memo Line" button, it required users to enter “PBSI__Tax_Value__c”. It should not. [Resolved in 1.677.]
8. When users tried to add a new count line for an item with a great amount of Lots, it showed “Collection size XXXX exceeds maximum size of 1,000.” error message. [Resolved in 1.677.]
9. 9. Simultaneous movement lines for the same item resulted in incorrect inventory detail totals. For instance, when two users completed two PWO’s for the same finished good at the same time, the two transactions happened at the same time and updated the inventory detail improperly.            [Resolved in 1.677.]
10. When using auto-generating serial numbers for finished goods on PWOs, if one of components was also serialized, the component serial number tracker field called “Parent Serial Number” was NOT populated with the parent serial number, which was auto-generated from completing the PWO.              [Resolved in 1.677.]
11. On Receive PO page, if the purchase order line “Discount” was blank, it showed the null pointer exception error message. [Resolved in 1.677.]
12. 12. Error happened when NOT using Lots and one single PWO was completed into two different locations. [Resolved in 1.677.]
13. After an item on the sales order line were staged in one location with serial numbers, users could not re-stage the sales order to another location with the same serial numbers. – Sales Order Staging is Ascent functionality since Ascent Release 1.619. If you want to learn about Staging Orders, please contact help@ascenterp.com. [Resolved in 1.678.]
14. 14.When users created a count line for a location and set the “Counted Quantity” to zero, serial numbers in that location were NOT removed from inventory. The expected result was the serial numbers in that location were updated to “In Inventory” = No. [Resolved in 1.678.] 
15. A drop-shipped sales order line still showed up on the Stage page. Items that were already drop shipped on a sales order line should not be allowed to show up on the stage page or the re-stage page. [Resolved in 1.678.]

Improvements:

1. We modified the Address format on Sales Order Pack Slips. [Available since 1.675.]
2. 2. We created a new custom setting: “Use SO Ship Loc for Delivery Address”. Once it is turned on, it will auto-populate delivery address by the Sales Order Ship To Location. [Available since 1.678.]