Commit 5dd7af44 authored by Łukasz Nowak's avatar Łukasz Nowak Committed by Rafael Monnerat

Disable constraint on Payment Transaction.

Note: Generic code shall have no constraints at all.

Conflicts:

	bt5/erp5_accounting/bt/revision
parent fc5b1b0d
......@@ -20,9 +20,6 @@
<portal_type id="Internal Invoice Transaction Line">
<item>AccountingTransactionLineConstraint</item>
</portal_type>
<portal_type id="Payment Transaction">
<item>AccountingTransactionConstraint</item>
</portal_type>
<portal_type id="Purchase Invoice Transaction">
<item>AccountingTransactionConstraint</item>
</portal_type>
......
......@@ -5,7 +5,6 @@ Balance Transaction | AccountingTransactionConstraint
Cash Register | BankAccount
Internal Invoice Transaction Line | AccountingTransactionLineConstraint
Internal Invoice Transaction | AccountingTransactionConstraint
Payment Transaction | AccountingTransactionConstraint
Purchase Invoice Transaction Line | AccountingTransactionLineConstraint
Purchase Invoice Transaction | AccountingTransactionConstraint
Sale Invoice Transaction Line | AccountingTransactionLineConstraint
......
  • Note: Generic code shall have no constraints at all.

    For future reference, "this is not so easy". These constraints are enabled by default because some reports from generic code and some actions from generic code need the document to comply to these constraints. If we disable the constraints, some reports and some actions (for example closing accounting period) might not do what they are supposed to do.

    /cc @rafael

  • /cc @romain as it seems the idea we had that time backfires.

    Edited by Łukasz Nowak
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment