save nested element draft against newest owner #16022
Open
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
When using the new
actionSaveNestedElementForDraft()
, a “No element was identified by the request.” error was thrown when trying to save a nested element edited in a slideout in the following case:(- if you reloaded the owner entry before editing the nested one, everything worked as expected)
This was happening because when the provisional draft of the owner element was created, and then the nested element was opened in a slideout, and then a change was made to that nested entry (triggering autosave) when that first
element/save-draft
call was made, the provisional draft of the nested entry had its ownership saved against the canonical of the owner entry and not the newly created provisional draft. Specifying theownerId
when opening the slideout fixes this problem.Related issues
n/a