- `delay` field on SO line moved to sale_stock, ignoring it for now
- avoid reusing the same bank account in 6.1 test, would cause a test
failure because the import would be skipped and the new partner
would have no bank account. Bank accounts should be unique in the
real world.
- log in DEBUG when a relationship record is skipped during EDI import
bzr revid: odo@openerp.com-20121019111100-dwf0crocqv43m3ij
As started in previous commits, in 7.0 there is no more
static storage of exported EDI documents, and they are
instead replaced by the improved portal - which will
provide the preview as well as export capabilities.
(The export might be added in a second phase)
bzr revid: odo@openerp.com-20121016122913-ndl0l36buhku3kxy
The EDI documents will now be generated on demand
and available from the Portal view of each document.
Instead of getting a link to a statically generated
EDI document, customers will receive a link to
the portal access to the document. They will be able
to signup on the portal the first time as well,
provided they are using the secure token that was
sent to them (i.e. the right link).
The link to pay online will be available in the
portal as well.
Still much to do, this is a small first step,
with edi.document renamed to edi.edi for
consistency, as it will not persist any
edi.document anymore.
bzr revid: odo@openerp.com-20121011152008-bht7ub6woaex0a7u
Now that res.partner does not allow name_create anymore
for usability reasons, we cannot depend on it, so we re-
implement it with create().
bzr revid: odo@openerp.com-20111220144131-1fbmx5vqckpofrkg
This is useful for transtyping documents, for example a sale.order
must be converted to a purchase.order when it is imported via EDI.
bzr revid: odo@openerp.com-20111006113319-ll5rfavzwzftkydb
Antony Lesuisse
Vo Minh Thu
Olivier Dony
Antonin Bourguignon
Saurang Suthar(OpenERP)
Pinakin Nayi (OpenERP)
Quentin (OpenERP)
Kuldeep Joshi (OpenERP)
Ankita Patel (OpenERP)
Christophe Simonis