Client number already set

[JamesKimmel]

Something seems to be off regarding the automatic number generation. It seems like deleted clients are not really deleted but in some kind of recycle bin. This is a fresh V5 installation with a csv import of 17 clients that were deleted afterwards.

I start with only one client. Client number 18.

Counter is set to 18, so the next client should be 19. This is what i get instead:

If it try to set test client from number 22 to 19, I get an error message, that this number is already taken:

Even after removing every client, going back to default settings by remove the “K” in front of the counter, the problem still persists. I cant generate a client with the numbers 1-17 and 19-21 for some reason.

[hillel]

Hi,

If you purge the client rather than delete them you’ll be able to re-use the number.

[JamesKimmel]

Thank you for the answer.
I did not know where to find the deleted clients to pruge them, so I purged everything in the system settings and it worked.

[pcstran]

@hillel

If you purge the client rather than delete them you’ll be able to re-use the number.

how to clean numbering from all clients and push to rename numbering?

It was not sorted out at the beginning so I would like to assign new numbers to all customers (who do have traffic), perhaps starting with S-001.

Is DB my new address?

How it looks like:

[hillel]

Maybe this will help:

How to re-number entries?

Hi There, Yes, a script will do the trick here, You’ll want to pull the expenses into the order that you need, so if you want to sort by date curl -X GET 'http://ninja.test:8000/api/v1/expenses?sort=date|asc' \ -H "X-API-TOKEN:your_api_token" \ -H "X-Requested-With: XMLHttpRequest" \ -H "X-API-SECRET:password" Then loop through them. curl -X PUT 'http://ninja.test:8000/api/v1/expenses/wMvbmOeYAl' \ -H "X-API-TOKEN:your_api_token" \ -H "Content-Type:application/json" \ -d '{"number":"new_nu…

Note: please create new posts to ask questions.