[0004212] Work Order Entry: fixed error when voided WO refence is reused.
authorJanusz Dobrowolski <janusz@frontaccounting.eu>
Wed, 10 Oct 2018 13:47:28 +0000 (15:47 +0200)
committerJanusz Dobrowolski <janusz@frontaccounting.eu>
Wed, 10 Oct 2018 14:05:04 +0000 (16:05 +0200)
manufacturing/includes/db/work_orders_db.inc

index f6d4400d839924a703ea9f8f26049e26541d9634..e1b0329edf34e1629ff8692b1a524c1c9ed8a12b 100644 (file)
@@ -287,7 +287,8 @@ function void_work_order($woid)
        void_wo_requirements($woid);
 
        // close workorder
-       $sql = "UPDATE ".TB_PREF."workorders SET closed=1,units_reqd=0,units_issued=0 WHERE id = "
+       // FIXME: due to bug in 2.4 db scheme (conflicting wo_ref unique key) we have to fix wo_ref here:
+       $sql = "UPDATE ".TB_PREF."workorders SET closed=1,units_reqd=0,units_issued=0, wo_ref=CONCAT(wo_ref, ' ', '".uniqid()."') WHERE id = "
                .db_escape($woid);
        db_query($sql, "The work order couldn't be voided");