`Scope Change` error preventing batch edit on certain tables

[emenslin]

Describe the bug
Original information on this issue: #5417 (comment). 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:

1. Go to queries
2. Select Gift as base table
3. Add any fields and save
4. Press batch edit
5. Validate the data set without making any changes
6. 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/

[bronwyncombs]

Reported by CSIRO on BoldDesk #739 with Collectors:

7.11.2

Long story short, we tried to use batch edit to update the yesNo1 field for these et al. collectors to be 'False' but got a 'scope change' error (see image below).

We assume this is something to do with the fact that collecting events can be across collections in a Specify7 instance. We tried to limit the query to the collection we were in but still got the same results/errors.

We tested editing a boolean field in the Collection Object Attribute table, and that seemed to work fine.

Can you please confirm the error for Collector yesNo1 is in relation to the cross-collection factor of Collecting Events? And also is there is a workaround we can use to update these collectors?

[grantfitzsimmons]

Re @bronwyncombs's latest comment from CSIRO– based on my examination of the code and from user testing, I believe the issue here is that 'Collector' is scoped to the 'Division', meaning you are able to edit collectors in other divisions within the same database. 'Collecting Event' is scoped to the 'Discipline', which is in conflict with this.

[grantfitzsimmons]

@acwhite211 @CarolineDenis Shouldn't we whitelist this case (Gifts) since we are using a similar approach for Loans? Both link to Division and Discipline, so this original issue here would be fixed.

specify7/specifyweb/backend/workbench/upload/upload_table.py

Lines 1090 to 1094 in 2a3b881

	# Edge case: Scope change is allowed for Loan -> division.
	# See: https://github.com/specify/specify7/pull/5417#issuecomment-2613245552
	def _is_scope_change_allowed(self, concrete_field_changes):
	if self.name == "Loan" and "division_id" in concrete_field_changes:
	return True