Content

On 2021-07-20 16:30, Bernat Brunet wrote:
> I have created Product01 and make an inventory of 100 units.
> You have a shipment in return (id:2) with 150 units and if you try to Assign, appear the loop origin warning.

Indeed it happens when Move.assign_try create a new move to be assigned.
So on each run it is a new id that is used for this new move.
I think we should find a way to distinct new records in Warning_.format
so we use another value than the id to build the key.
I think to distinct we could the `Transaction.create_records` and to
replace the id we could use the value of the fields excepted for binary.