Skip to content

[FIX] account_invoice_start_end_dates: avoid check on deferred lines - #367

Open
tobiaszehntner wants to merge 1 commit into
OCA:18.0from
acsone:18.0-fix-account_invoice_start_end_dates-tze
Open

[FIX] account_invoice_start_end_dates: avoid check on deferred lines#367
tobiaszehntner wants to merge 1 commit into
OCA:18.0from
acsone:18.0-fix-account_invoice_start_end_dates-tze

Conversation

@tobiaszehntner

Copy link
Copy Markdown
Contributor

The constrains raises for generated deferred entries even though the posted entry has valid dates.

@OCA-git-bot

Copy link
Copy Markdown
Contributor

Hi @alexis-via,
some modules you are maintaining are being modified, check this out!

@tobiaszehntner
tobiaszehntner marked this pull request as draft March 17, 2026 13:29
@tobiaszehntner
tobiaszehntner force-pushed the 18.0-fix-account_invoice_start_end_dates-tze branch from 1f8421a to 97e8af8 Compare March 17, 2026 14:07
@tobiaszehntner

tobiaszehntner commented Mar 17, 2026

Copy link
Copy Markdown
Contributor Author

Hello @alexis-via
Could you confirm if this is the best way to narrow the constrains? Our issue is with Odoo Enterprise (account_accountant) but I wouldn't be able to check on those specific fields inside the OCA module.
Thanks, Tobias

@tobiaszehntner
tobiaszehntner marked this pull request as ready for review March 17, 2026 14:12
@tobiaszehntner
tobiaszehntner force-pushed the 18.0-fix-account_invoice_start_end_dates-tze branch from 97e8af8 to 3f35375 Compare March 17, 2026 14:14
The check should not be raised on every account.move.line. One issue is with Odoo Enterprise: The constrains raises for generated deferred entries (account_accountant/models/account_move.py:114) even though the posted entry has valid dates.
@tobiaszehntner
tobiaszehntner force-pushed the 18.0-fix-account_invoice_start_end_dates-tze branch from 3f35375 to 96f84ca Compare March 20, 2026 08:50
@github-actions

Copy link
Copy Markdown

There hasn't been any activity on this pull request in the past 4 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 PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions Bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 19, 2026
@tobiaszehntner

Copy link
Copy Markdown
Contributor Author

@alexis-via could this be merged so it's not lost?

@github-actions github-actions Bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 2, 2026
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.

2 participants