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

transaction.number_next #2610

Closed
InteliClic opened this issue Aug 27, 2022 · 3 comments
Closed

transaction.number_next #2610

InteliClic opened this issue Aug 27, 2022 · 3 comments

Comments

@InteliClic
Copy link

Akaunting version

3.0.6

PHP version

8.1

Operating system

Ubuntu 14.04

Steps to reproduce

Import data which changes the auto-increment of the transactions table creates an annoying error on the add payments popup and in add income/expense transaction.

In the following images you can see the issue:
Screenshot 2022-08-27 094938
Screenshot 2022-08-27 094953
tings table.

Expected result

Add a payment without issue.

Actual result

Add a payment prompts an error.

Additional comments

I managed to fix this issue very easily by going into the database and changing the settings.transaction.number_next but it seems to me that Akaunting should check the auto-increment on the database and update the row in the set.

This ended up happening because I had to manually import the old Akaunting system. Quite frustrating that the export / import didn't work either. On the old system kept getting an error but since that's not supported seems pointless to explore that.

Relevant log output

No response

@barthmania
Copy link

I have the exact same issue since the V3 update, I have to manually input a transaction number for every single invoice or expense I add... Which is very annoying.

@cuneytsenturk
Copy link
Member

You can update on database this number, settings table key = transaction.number_next

@WillyReyno
Copy link

@cuneytsenturk This issue also happens on the hosted version https://akaunting.com/, where we don't have access to the database. How can we fix that ?

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

No branches or pull requests

4 participants