admin/raven
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

case 4653 - deleting a record still in use is refused with "in use by" instead of a server error

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
John Cardinal
2026-10-31 14:57:42 -07:00
parent 6d3b169f23
commit e8b3486a9e
16 changed files with 137 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/8.0/ayanova/docs/changelog.md
View File

@@ -18,6 +18,7 @@ IN PROGRESS
- Server: in some cases the automatic backup could be skipped for one day after the AyaNova server was restarted or a manual backup was made; it now always runs at the next chosen [backup time](ops-form-backup.md#backup-time).
- Server: opening a record that has since been deleted (for example from an old link) now shows a "not found" message instead of a server error, and a report printed for records of which some have since been deleted now prints the remaining ones instead of failing.
- Server: in some cases deleting a record that is still in use elsewhere (for example a customer, unit, part or rate used on a work order, quote or PM) gave a server error; it now always says which kind of record is using it.
### AyaNova 8.3.0