Comment 2 for bug 783994

Revision history for this message
Amit Parik (amit-parik) wrote : Re: [6.0] account_move_line: uninitialized period_id

Hello Stephane,

I have checked your issue at my end.
But all are working fine and I am not able to faced any traceback.

See the _check_date function and print the vals it gives o/p like this

 {'analytic_lines': [], 'statement_id': False, 'currency_id': False, 'date_maturity': False, 'narration': False, 'partner_id': 7, 'blocked': 0, 'analytic_account_id': False, 'journal_id': 1, 'tax_code_id': False, 'debit': False, 'ref': False, 'account_id': 9, 'period_id': 2, 'date_created': '2011-05-19', 'date': '2011-01-24', 'move_id': 8, 'tax_amount': False, 'name': 'eeee', 'account_tax_id': False, 'credit': False, 'amount_currency': False, 'quantity': False}

Which have the period_id because the "period_id" is required field in account.move.line so no need to assign it again as a False.

That's why in any case I am not faced any traceback so would you please provide your side example or proper steps in which you have faced the traceback.

Thanks and Waiting for your reply!