Created on 2020-12-15.18:58:07 by ced, last changed 3 weeks ago by ced.
No this is a closed issue.
To correct the problem of filtering on the product for the detection of quantity issue, I push on the review even if it is closed?
New changeset 38b2018c006d by Cédric Krier in branch 'default': Add stock_quantity_issue module https://hg.tryton.org/tryton-env/rev/38b2018c006d
New changeset 3962b9c1eb5b by Cédric Krier in branch 'default': Add stock_quantity_issue module https://hg.tryton.org/readthedocs/rev/3962b9c1eb5b
New changeset e1e738419309 by Cédric Krier in branch 'default': Add stock_quantity_issue module https://hg.tryton.org/modules/stock_quantity_issue/rev/e1e738419309
New changeset 532ecf3087f9 by Cédric Krier in branch 'default': Add stock_quantity_issue module https://hg.tryton.org/modules/stock/rev/532ecf3087f9
Not really because it is really the list of products. Also I think it is wrong to think in terms of difference between shipped quantity and stock quantity. It is a reduction of the problem that does not picture the complexity of time events.
Could it be possible to have quantity shipped/sell in product list ? Now it displays only stock quantity and forecast quantity. It would be useful to see difference between quantity shipped and quantity in stock that leads to issue.
On 2021-02-12 10:05, Maxime Richez wrote: > It would be useful to have a column Party (function field). In case of production issue, it would be empty, but for shipment problem, it allows to identify quickly party that will have problem with his order. I do not think it is a good think because: * There is already an exception for production (but more documents could be added) * After the customer, there will be the address, the origin etc. So for me the record name of the shipment is enough and it can be opened to see details. Also as I said in the review, all issues must be solved and they must be done one by one.
It would be useful to have a column Party (function field). In case of production issue, it would be empty, but for shipment problem, it allows to identify quickly party that will have problem with his order.
For me this is not related to this change.
After installing the module and launching the 'Generate Stock Quantity Issue' wizard. Is there something to do before launching the wizard?
Traceback (most recent call last): File "/trytond/wsgi.py", line 111, in dispatch_request return endpoint(request, **request.view_args) File "/trytond/protocols/dispatcher.py", line 47, in rpc return methods.get(request.rpc_method, _dispatch)( File "/trytond/wsgi.py", line 78, in auth_required return wrapped(*args, **kwargs) File "/trytond/protocols/wrappers.py", line 131, in wrapper return func(request, pool, *args, **kwargs) File "/trytond/protocols/dispatcher.py", line 181, in _dispatch result = rpc.result(meth(*c_args, **c_kwargs)) File "/trytond/wizard/wizard.py", line 314, in execute return wizard._execute(state_name) File "/trytond/wizard/wizard.py", line 345, in _execute result = self._execute(transition()) File "/trytond/modules/stock_quantity_issue/stock.py", line 352, in transition_generate QuantityIssue.generate_issues(warehouses=self.start.warehouses) File "/trytond/modules/stock_quantity_issue/stock.py", line 251, in generate_issues if product_quantity.quantity < 0: File "/trytond/model/fields/function.py", line 129, in __get__ return super().__get__(inst, cls) File "/trytond/model/fields/field.py", line 339, in __get__ return inst.__getattr__(self.name) File "/trytond/model/modelstorage.py", line 1623, in __getattr__ read_data = self.read(list(index.keys()), list(ffields.keys())) File "/trytond/model/modelsql.py", line 859, in read getter_results = field.get(ids, cls, field_list, values=result) File "/trytond/model/fields/function.py", line 105, in get return dict((name, call(name)) for name in names) File "/trytond/model/fields/function.py", line 105, in <genexpr> return dict((name, call(name)) for name in names) File "/trytond/model/fields/function.py", line 98, in call return method(records, name) File "/trytond/modules/stock/product.py", line 546, in get_quantity assert date != date_start AssertionError Fault:
status: chatting -> resolved
status: resolved -> chatting
|2021-03-21 13:00:21||roundup-bot||set||messages: + msg65709|
|2021-03-21 13:00:19||roundup-bot||set||messages: + msg65708|
|2021-03-21 13:00:14||roundup-bot||set||messages: + msg65707|
nosy: + roundup-bot
status: testing -> resolved
|2021-02-27 19:39:36||reviewbot||set||messages: + msg65010|
|2021-02-24 09:45:59||ced||set||messages: + msg64808|
|2021-02-23 11:43:49||reviewbot||set||messages: + msg64784|
|2021-02-18 16:02:46||mrichez||set||messages: + msg64689|
Showing 10 items. Show all history (warning: this could be VERY long)