#1026 1.3 only: - Vendor pricelist save clears previous prices and lead times, sku, curr

1.3
closed-works-for-me
Chris Travers
None
7
2014-02-26
2014-02-01
Pongracz Istvan
No

I filled up a list of products with vendor and its price and lead time.
Reading back a product shows the vendor and earlier entered price, SKU, currency, lead time.

I went to the Vendor screen and asked a pricelist:
- it shows 0 as previous purchase price (expected: if no vendor invoice, the entered prices should appear on this list as list price and as shown in the partsvendor table, where the price exists, but not visible on the screen)
- lead time shown as entered in the product screen, 0 if I forgot to enter

The issue:
- I entered new lead times instead of 0
- Click on save

The result:
- all lead times and earlier entered list prices, SKU of the vendor wiped out, cleared, lost

partsvendor table:
- wiped out:partnumber, leadtime, lastcost, curr

Expected result:
- the save should save new values instead of wipes everything

Notes:
- I have new DBObject.pm for sequences.

Discussion

  • Chris Travers
    Chris Travers
    2014-02-26

    • assigned_to: Chris Travers
     
  • Chris Travers
    Chris Travers
    2014-02-26

    • summary: 1.3 - Vendor pricelist save clears previous prices and lead times, sku, curr --> 1.3 only: - Vendor pricelist save clears previous prices and lead times, sku, curr
     
  • Chris Travers
    Chris Travers
    2014-02-26

    does not happen on 1.4

     
  • Chris Travers
    Chris Travers
    2014-02-26

    I could not reproduce this on 1.3.37 or 1.3.38. Closing as works for me. I did however notice a bug in handling multiple vendor lines.

     
  • Chris Travers
    Chris Travers
    2014-02-26

    hmm on the second bug I was looking at the wrong window (my 1.4 window).

    Closing this as works for me.

     
  • Chris Travers
    Chris Travers
    2014-02-26

    • status: open --> closed-works-for-me
     
  • Chris Travers
    Chris Travers
    2014-02-26

    (if you have time and are still seeing this problem on 1.3.38 let's get together to debug it)