Since update, I can't open fiscal year

Support User
1

Since updating Tryton to the latest version (7.6.5), I can’t renew the fiscal year:

image
image643×169 10.9 KB

When I try to create a new fiscal year, the field for selecting a sequence doesn’t find any sequence. However, these sequences exist in the database and were activated without problem for the previous year.

Any clue on how to debug this? How can I check why the sequences are not found?

2

It looks like the problem comes from the fact that the sequence you expect to use does not match the domain of the field https://foss.heptapod.net/tryton/tryton/-/blob/branch/default/modules/account/fiscalyear.py?ref_type=heads#L51 . Please check that the sequence you want to use for the new fiscal year satisfies all of the following:

  • Has sequence_type equal to account.sequence_type_account_move (the internal id account, sequence_type_account_move).
  • Belongs to the same company as the fiscal year (company = current company).
  • Is marked as strict, because since 7.4 the accounting move sequences must be strict to avoid gaps.

If any of these conditions is not met, the sequence will not appear in the selection list for the fiscal year.

3

Probably the problem is that the “Account Move Sequence” used on your fiscalyear does not have a company. Adding the company to the sequences should fix the problem.

P.S: Note that if you open the sequence directly from the fiscalyear sequecnes you will seee the company field set (due to domain inversion) but if you open it from the sequences menu item you will see it empty. Make sure to check from there to avoid confusion.

4

Thanks everyone for your answers.

I couldn’t find where to mark the sequence as strict, and the sequence already had a company set.

However, I opened the sequence used for 2025, changed its name slightly, and saved it. After that, it became selectable in the fiscal year sequence search field.

I’m not sure what happened at the database level, but simply re-saving the sequence seems to have fixed the issue.