Skip to content
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

Bug in Fiscal Year Closing module in odoo version 14 #280

Closed
Evaguadaltech opened this issue Nov 9, 2023 · 7 comments
Closed

Bug in Fiscal Year Closing module in odoo version 14 #280

Evaguadaltech opened this issue Nov 9, 2023 · 7 comments
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@Evaguadaltech
Copy link

Evaguadaltech commented Nov 9, 2023

error-cierre-ejercicio-comufri
Hello, when we have created a year-end closing and we have added the transaction configuration. When saving or calculating the year-end closing it gives the attached error. And it does not create the year-end closing.

Thank you.

@Evaguadaltech
Copy link
Author

Buenos días, ¿se ha podido corregir a dia de hoy la incidencia que he indicado en odoo 14?

Gracias.

@mde-scopea
Copy link

Hi, same issue.
I thinks it's linked to PR #199 for the migration into v14

Any chances to revert commit fb4c3ee ?
I don't understand the need for this code :)
And w/o this code, it seems to work fine.

@mde-scopea
Copy link

How to reproduce:

  • settings => for current user, set checkbox on user profile 'Show Accounting Features - Readonly'
    image

  • Invoicing / Accounting / Fiscal year closing => create new entry:
    image
    image

Result: Impossible to Save or Calculate => crash with traceback

@Evaguadaltech
Copy link
Author

Hola, el error lo daba cuando el campo Destination account lo pongo vacio cuando el campo Move type es Closing. ¿me habeis entendido?

Gracias.
Un saludo.

@mde-scopea
Copy link

@Evaguadaltech any chance to test the PR #294 ?

@Evaguadaltech
Copy link
Author

Hola, los cambios que has indicado los he probado en local y me han funcionando correctamente.

Gracias.
Un saludo.

Copy link

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.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Sep 15, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

2 participants