-
Notifications
You must be signed in to change notification settings - Fork 40
Description
Describe the bug
Original information on this issue: #5417. This was specifically handled for loans previously, but there are multiple tables that are also impacted by this that should be addressed. I was able to consistently recreate this two ways but I'm sure there are other tables that are also impacted, first if a batch edit data set is created with gift as the base table, and second, if collecting event is the base table and if collection objects are included.
To Reproduce
Steps to reproduce the behavior:
- Go to queries
- Select Gift as base table
- Add any fields and save
- Press batch edit
- Validate the data set without making any changes
- See error
Expected behavior
I'm not sure about every case since I don't know every table that is impacted, however, I feel like either there should be no error when batch editing these tables or if there is good reason to not allow the tables to be edited then they should be read-only so the user can still see them even if they cannot be edited (specifically in cases where it is a relationship that is causing the error such as collection object on a collecting event data set).
Screenshots
Gifts:
08-14_15.23.mp4
Collecting Event:
Please fill out the following information manually:
- OS: Windows 11
- Browser: Chrome
- Specify 7 Version: 7.11.1
- Database Name: ojsmnh
- Collection name: fossil invertebrates
- User Name: spadmin
- URL: https://ojsmnh2025071720250807-main.test.specifysystems.org/specify/