Skip to content

Merging onboarding level 1 tasks #4809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

shzi-odoo
Copy link

  • Created a new field in the company to separately track the PAY sequence Id's instead of batch Id's
  • Created a new function to get the next available ID
  • Changed the group of the menu items related to accounting analytics if not activated
  • Inside payment registery file I set the new lable of communication field which is shown at the memo to be with the new payment group Id's

…eld for group payments to use in group payment memo
@robodoo
Copy link

robodoo commented Jul 3, 2025

This PR targets the un-managed branch odoo-dev/odoo:18.0-rd-accounting-onboarding-malb, it needs to be retargeted before it can be merged.

Copy link

@malb-odoo malb-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do a branch by task it will be easier in term of review 😄

@@ -49,3 +49,5 @@ package.json
/man/
/share/
/src/

venv/

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unnecessary diff that

@@ -167,6 +167,20 @@ class ResCompany(models.Model):
'prefix': 'BATCH/%(year)s/',

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the solution would be to change the BATCH to -> PAY and modify the test accordingly

use group_payment_sequence_id to get it (eventually create it first): e.g PAY/2025/00001
'''
self.ensure_one()
return self.sudo().group_payment_sequence_id.next_by_id()

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need for that if the field is gone 😄

@malb-odoo
Copy link

Also commit message should follow those guidelines 😄
https://www.odoo.com/documentation/17.0/contributing/development/git_guidelines.html

@malb-odoo
Copy link

i will close this since it's a merge of multiple task, we will say it's the one for the group of analytic 😄

@malb-odoo malb-odoo closed this Jul 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants