SearchKit - Fix saving created/modified fields #26484
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.
Overview
Fixes saving created/modified info when updating a savedSearch in SearchKit.
Before
After
Fixed.
Technical Details
Don't select created/modified id or date fields when loading SavedSearch so they don't get sent back as values. The BAO will then be free to auto-fill them.
Comments
I think there are some larger issues here where we need to teach APIv4 not to mess with fields set to
<readonly>
in the schema. But this PR is the most minimal change and can be safely merged regardless of what other stuff we end up doing.