V5.0 - Asset-ID wont increase automatically

[GustelDE]

Hi,

with V5, if I copy an Asset, the new Asset-ID wont increase to the next free number.
It stays the same number and says, Asset-ID already present, I must enter the next (free) number manually.

Behaviour not with V4.x

Additional Information:
It works for the first copied Asset, but for all further copies, the number stays the same.
As above: 888 was the next free number, but 889 showed still 888.

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

[jovibroz]

I'm at 303 and duplicate works, 304, 305 no problem here..

Though, I'd like the counter to sense the highest used number. If I delete the test assets 304,305 I just created, next auto-increment number will still be 306. So I have to remember to manually turn back the counter if deleting an asset.

[GustelDE]

Hi, im at 887. If I copy an Asset, the new one gets 888. Thats right.
The next copy gets 888 again, and all new copies will get 888. This is reproducible with V5.0.0 and V5.0.1 With V4.9.5 everything worked fine!

The only way the counter goes up ist to:
docker exec -it snipe-it_snipe-it_1 sh
And then execute:
php artisan cache:clear
Then it works for the next number. The next copied Asset gets 889, but it stuck at 889 again untill I do php artisan cache:clear again...

As told, Docker-Compose-Version V5.0.1

[GustelDE]

Screenshots:

And under Settings -> Asset Tags no changes are possible!
Everything triggers an Error!

Unfortunately I have to consider V5.0.0 and V5.0.1 as NOT stable!
There is almost everything broken, its a public Beta, but far away from a Stable :/

[GustelDE]

Problem partially solved by this:
#8578

Only the missing prefix or 000 persist.

[snipe]

Unfortunately I have to consider V5.0.0 and V5.0.1 as NOT stable!
There is almost everything broken, its a public Beta, but far away from a Stable :/

We have customers already using v5.0.1, so that seems unlikely, but I would like to get to the bottom of this.

If you turn debug on and enable the debug bar, what does the message bag say when you try to ave the settings?

[xam-ps]

I can confirm, the problem with the missing leading zeros.

That bug is still existing in Version 5.0.9

[LEOkonami]

I have the same issue and I think I found the source of this issue...
when I go to Asset Tag Settings I can see the "Next auto-increment" stuck on 595...

I get this error message and I have an asset with the number and I can't even change the number (Getting: Error: Please check the form below for errors
)

[LEOkonami]

@snipe The messages are empty, I can't see any error...

[LEOkonami]

@snipe @GustelDE Any updates about this issue, super annoying :)

[DPNADM]

I am having this same issue in 5.1.4.

It will not progress to the next asset ID. I have to manually change it. In the admin settings, I cannot set it to use a higher number, it just falls back. No changes I make to the auto-increment settings will stick.

[Viiviv]

Having issues with auto-increment too. Seems to be stuck in an used tag.
Also changing the next auto-increment in the menu doesn't change in the UI.
It does however change in the database settings next_auto_tag_base

Version v5.1.4 - build 5886

[DPNADM]

I have this same issue. I'm updated up to v5.1.8 - build 6227 and the issue persists. I've had this issue ever since upgrading to 5.1.4 which was my first 5.x version. In the admin settings within the GUI, I cannot even set the settings for the incrementing asset tag. Any changes are reverted and not stored.

I am wondering if there is some sort of permission issue here. I can't seem to change some other admin settings since the update either. Any changes revert back. I do not see error messages when I attempt to change and save. Going back into the setting that was changed just shows the previous settings are still set.

There are no issues adding assets, models, or other items to Snipe-IT...just changes to the admin settings appear to be an issue.

[DPNADM]

Actually, I was able to resolve just by using the commands in the "common issues" documentation.

https://snipe-it.readme.io/docs/common-issues

composer dump-autoload
php artisan cache:clear
php artisan config:clear
php artisan route:clear
php artisan debugbar:clear
php artisan event:clear
php artisan view:clear
php artisan optimize:clear
php artisan clear-compiled

Snipe-IT Documentation

Common Issues

These commands should be run from your Snipe-IT project root, just like every other cli command we mention. They should not need to be run as root/sudo/admin.Or to run them as a one-liner all at once:These commands clear out cached service files that help speed up modern PHP applications but can a...

[LEOkonami]

I fixed the issue with some Github login and shit, not sure anymore what I did it just worked.