Fix saving error with custom permissions in O2M fields #13998
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a simple bug fix for #13765 and #13997. When editing an item with relation fields and also have RBAC controls, users may get "You don't have permission to access this" error. The reason is when user click the relation items in the main item view, the list-o2m.editItem() will set the editsAtStart to the displayItem which contains the related fields. In fact, we just need to pass the key value of this item as the editsAtStart as when the drawer pops up, the value will be fetched from backend. So the fix is also simple, just remove all unrelated fields from the displayItem except the key field.
Fixes #13765
Type of Change
Requirements Checklist
If adding a new feature: