snipe-it
snipe-it copied to clipboard
snipe
Asset Model Default Values Checkbox Error
Debug mode
- [X] I have enabled debug mode
- [X] I have read checked the Common Issues page
Describe the bug
When attempting to set a default value in a new asset, if a checkbox custom field is selected the default value is rejected and any previously saved default values are removed. An error of "Error validating default fieldset values." is shown.
Reproduction steps
- Create a custom field with the checkbox type. Populate with options.
- Assign the custom field to a fieldset.
- Create a new asset model.
- Select the fieldset for the new asset model.
- Check the option to include default values.
- Check one or more of the checkbox values.
- Attempt to save the asset.
Expected behavior
The checked values should be saved and used as the default when creating a new asset with that model.
Screenshots
Custom field for printer functions.
Fieldset with the field contained therein.
Attemping to add the default value to a newly created asset model.
The error the occurs when trying to save.
Snipe-IT Version
6.3.0
Operating System
Hosted
Web Server
Hosted
PHP Version
8.1.23
Operating System
Windows
Browser
Edge
Version
121.0.2277.83 (Official build) (64-bit)
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
Wanted to add a comment saying I am having the exact same issue. I am trying to set a field for monitors and PCs showing what video ports they have as a checkbox field, so when I need to look for replacements, I can just easily find something that is compatible with it.
Get that exact same issue when trying to save the model default value (so I don't need to manually add it multiple times for same model monitors)
Hopefully this gets a reply soon. @uberbrady thank you in advance, I know the team is hard at work with multiple tickets and updates, the app is otherwise great aside from this one issue I have.
Just tested on the demo version for V6.3.4 and I believe this has been fixed.