:thinking_face: ... re: Testing New Releases, do a...
# releases
r
🤔 ... re: Testing New Releases, do any of y'all test transactions already in flight (i.e. Sales Orders Pending Approval or Fulfillment created prior to the release preview)? I wish we had, as we'd have seen a bug that took us down Friday. Our issues, both related to fulfillment of Sales Orders: SO's created via web services (on a different form) after 2018.2 up to our new release date lost the value presented for "FULFILLED." The value was changed to null on all sales orders, open or closed. For the open orders, all were pushed to Pending Billing when a workflow saved the record. Further, the defect disassociated what was actually fulfilled from the item fulfillment; GL was fine, but no items were shown on the fulfillment nor the sales order (but the detail did appear on invoices). For the open orders, we had to write a script to go to each order (1093 records) and re-enter the item number for each line to essentially flash the record (about 7000 lines). For the detached values, we've got a hot fix coming for defect 536765.
c
not to kick someone while they are down but this could have helped: https://www.assertology.com/
r
The demo shows this working for newly created records, all of which were fine.
c
New records always work..at least it seems like that. Pipelines always break and it was something we tested at my former employer every release
👍 1
Disclosure: A friend owns assertology: the product has a feature where you can point it back to product so whe its copied for RP you get to run live tests same day
in your case I would have walked a couple of orders to completion