Am 07.02.2017 um 15:59 schrieb Cédric Krier:
> On 2017-02-07 15:21, Ul wrote:
>>
>> So it is going to be a big tree, that is not possible to know before.
>
> As far as I see it is just two trees on lot based each one on a
> Many2Many using the production moves in a table query.
> So it is about to show in a Many2Many the lot used in the output moves
> of production which uses in the input moves the lot.
> I think such Model can be written using a ModelSQL.table_query quite
> easily.
With a ModelSQL.table_query i can combine the necessary tables basically
the stock.move and the stock.lot. It would be nice to pull in Infos from
ShipmentIn and from Production, like the effective date or the supplier,
but that isn't that important.
I would add fields.Function as 'parent' and 'childs', that it is
displayed as a tree not a plain list.
I see the main Problem in filtering the records to decide witch records
to show because they belong in this 'in-heritage'-tree.
My approch would be a loop starting at the 'root'-lot looking up the
lots that went into the production that produced the root-lot. and doing
the same with the lots in the result and again with this results until
every lot in the tree is processed that came out of a production.
here is an example how i imagine the output, of course with some more
columns like product, production-date and so on:
XY
AB
GH
JK
KL
WE
UI
CD
WE
NM
Such development could be included in the base of Tryton.
>
What could be included in the base? a filter to filter a table for
multi-stage relations? Perhaps it could be a special kind of domain
operator...
That would be nice, but i think I'm not able to do it myself or pay it
right now...
--
You received this message because you are subscribed to the Google Groups
"tryton" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tryton/0712fd78-140c-5cd6-2add-e09c73df6022%40gmx.de.
