[16.0] The sequence is not set at confirmation
mourad-ehm opened this issue · 6 comments
Module
account_move_name_sequence
Describe the bug
1-When I confirm an invoice I got "The operation cannot be completed: A move can not be posted with name "/" or empty value
Check the journal sequence, please".
2-In oca runbot I got an other behaviour. There is no message but the sequence in not taken in to account.
Concerning the first case, in debug mode in my dev env, the "name" field compute are triggered before state value changement if I change also date otherwise is not triggered by confirm action if date don't change but exception is triggered !
To Reproduce
16.0:
Steps to reproduce the behavior:
##1.Change sequence prefix of Customer Invoices journal
2. create an new invoice.
3. Compare invoice number with journal sequence definition.
Expected behavior
invoice number must correspond to journal sequence definition.
ping @alexis-via , @moylop260 , @frahikLV , @RodrigoBM , @pedrobaeza
No, I didn't do anything else. I just modified the parameters of the sequence (prefix: TTT...).
Otherwise I remarked that in my base the date range contain 2018. Is possible that someone have change some thing in database before I did the test.
Dear all,
I have the same problems. Can you please explain me how to fix that issue. Thank you!
I change it to 16.0.2.0.0 but now have another error when I make an invoice.
The operation cannot be completed: new row for relation "account_move" violates check constraint "account_move_name_state_diagonal"
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.
It was already fixed for lastest fixes
Please, feel free to re-open it if you still can reproduce it