Commit 473b5942 by mushishixian

恢复

parent b35c33b9
......@@ -6,6 +6,7 @@ import (
"fmt"
"github.com/ichunt2019/go-rabbitmq/utils/rabbitmq"
"github.com/imroc/req"
"scm_server/cmd/queue/sync_status/product"
"scm_server/configs"
"scm_server/internal/common"
"scm_server/internal/logic"
......@@ -75,9 +76,9 @@ func (t *RecvPro) Consumer(dataByte []byte) error {
if err = SyncCustomerData(operateType, customer); err != nil {
goto ERR
}
//if err = product.SyncErpStatus("customer", customer.ErpId); err != nil {
// goto ERR
//}
if err = product.SyncErpStatus("customer", customer.ErpId); err != nil {
goto ERR
}
return nil
ERR:
return logic.DealSyncError(dataByte, customer.ErpId, "customer", err)
......
......@@ -6,6 +6,7 @@ import (
"fmt"
"github.com/ichunt2019/go-rabbitmq/utils/rabbitmq"
"github.com/imroc/req"
"scm_server/cmd/queue/sync_status/product"
"scm_server/configs"
"scm_server/internal/common"
"scm_server/internal/logic"
......@@ -78,9 +79,9 @@ func (t *RecvPro) Consumer(dataByte []byte) error {
if err = SyncGoodsData(operateType, goods); err != nil {
goto ERR
}
//if err = product.SyncErpStatus("material", goods.ErpId); err != nil {
// goto ERR
//}
if err = product.SyncErpStatus("material", goods.ErpId); err != nil {
goto ERR
}
return nil
ERR:
return logic.DealSyncError(dataByte, goods.ErpId, "goods", err)
......
......@@ -6,6 +6,7 @@ import (
"fmt"
"github.com/ichunt2019/go-rabbitmq/utils/rabbitmq"
"github.com/imroc/req"
"scm_server/cmd/queue/sync_status/product"
"scm_server/configs"
"scm_server/internal/common"
"scm_server/internal/logic"
......@@ -76,9 +77,9 @@ func (t *RecvPro) Consumer(dataByte []byte) error {
if err = SyncSupplierData(operateType, supplier); err != nil {
goto ERR
}
//if err = product.SyncErpStatus("supplier", supplier.ErpId); err != nil {
// goto ERR
//}
if err = product.SyncErpStatus("supplier", supplier.ErpId); err != nil {
goto ERR
}
return nil
ERR:
return logic.DealSyncError(dataByte, supplier.ErpId, "supplier", err)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or sign in to comment