-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Require serial numbers to be unique #5751
Comments
This is currently on develop. Can you give it a try and test it out? Check the Settings > General box for unique serials, and test with duplicated serials and also nulls. |
That'll work exactly as needed! Thanks for the quick turn around! |
@snipe but then what about already created assets? |
@sid8000 it won’t have any understanding of assets that already exist that have duplicate serials, but if you try to save an existing asset with a pre-existing serial, it will throw an error instead of letting you save it. |
what about if you import? with the same serial ? there is no error in it |
@markwizer the expectation is you verify the data before you upload I would assume. Importing isn't an ordeal for me, but you can easily search for duplicates in Excel/LibreCalc etc and correct anything before it goes into the database. @snipe thanks again! |
@Jarli01 I think snipe can add that feature that it will not proceed on importing whenever it has the same serila, like an error message serial must be unique |
@markwizer she might be able to add it as a feature of the importer function, but this should be controlled long before the data ever reaches a production database. Clerical controls can make this a non-issue as it's trivially easy to highlight duplicate values. |
@esspeecy410 you can opt to enable this or not. Full company support allows this to occur in separate companies as well. Trying to add in the random cases of taking what should be a UUID in the world of serial numbers and saying that it should also account for reasons XYZ doesn't really fit. P.S. please create your own ticket and reference this one. |
It is not working. |
@aledr Please don’t frankenthread. A lot has changed since the last post here. Open a new issue and fill out the issue template so we can help you. |
Server (please complete the following information):
Snipe-IT version | v4.4.2 build 3666 (gaa5003d29)
Software License | AGPL3
PHP Version | 7.1.19
Laravel Version | 5.4.35
CentOS 7
Is your feature request related to a problem? Please describe.
As it is now, if a asset tag is removed from a physical device and someone lazily just creates a new asset tag for the device without searching for the serial number you end up with duplicate assets.
By using the serial number as the unique identifier (in my case) we would never have duplicate assets with the same serial number (just wouldn't ever occur in our case).
To protect from laziness, using the serial number as a unique field would protect from the "whoops I was lazy and didn't check" cases.
Describe the solution you'd like
A feature option that is set at the organization level (so different companies within an organization could have the option to individually set) if serial numbers must be unique before a new asset is added/created.
Describe alternatives you've considered
Based on the types of assets we have, our focus is on serial number, everything that is an "Asset" has a unique serial number even if the devices are from different manufacturers. Model numbers can match, sure but the serial is always unique.
For items so trivial that don't have serial numbers they get added to the system as an accessory and just get accounted for in that manner.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: