From 0230d2c4190bc4ff6208c6f46698ad975fdd66c0 Mon Sep 17 00:00:00 2001 From: Romain Courteaud <romain@nexedi.com> Date: Mon, 29 Oct 2007 09:29:12 +0000 Subject: [PATCH] Do not try to create meaningfull IDs, as order movement can be hierarchicals git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@17236 20353a03-c40f-0410-a6d1-a30d3c3de9de --- product/ERP5/Document/OrderRule.py | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/product/ERP5/Document/OrderRule.py b/product/ERP5/Document/OrderRule.py index f6ea643908..0700000439 100644 --- a/product/ERP5/Document/OrderRule.py +++ b/product/ERP5/Document/OrderRule.py @@ -111,16 +111,11 @@ class OrderRule(DeliveryRule): related_order = movement.getOrderRelatedValue() property_dict = self._getExpandablePropertyDict(applied_rule, movement) if related_order is None: - if movement.getParentUid() == movement.getExplanationUid(): - # We are on a line - new_id = movement.getId() - else: - # We are on a cell - new_id = "%s_%s" % (movement.getParentId(), movement.getId()) # Generate a simulation movement + # Do not try to create meaningfull IDs, as order movement can be + # hierarchicals applied_rule.newContent( portal_type=movement_type, - id=new_id, order_value=movement, order_ratio=1, delivery_ratio=1, -- 2.30.9