Grid OnSave event (Client API reference)
The OnSave
event occurs before sending the updated information to the server, and when any of the following occurs:
- There is a change in the record selection.
- The user explicitly triggers a save operation using the editable grid's save button.
- The user applies a sort, filter, group, pagination, or navigation operation from the editable grid while there are pending changes.
Some important points to consider for the OnSave
event:
- If a user edits multiple columns of the same record in sequence, the OnSave event will only be fired once to ensure optimal performance and form behavior compatibility.
- Editable grid and the parent form have separate save buttons. Selecting the save button in one will not save changes in the other.
- Editable grid does not save pending changes when navigation operations are performed outside of its context. If the control has unsaved data, that data may be lost. Consequently, the
OnSave
event may not fire. For example, this could happen when navigating to a different record using a form lookup column or through the ribbon. - Selecting the refresh button in the editable grid causes it to discard any pending changes, and the
OnSave
event won't be fired. - Editable grid control does not implement an auto-save timer. Editable grid suppresses duplicate detection rules.
Note
The OnSave
event for appointment, recurring appointment, or service activity records will cancel the save operation and use the Book
message to persist the change rather than Create
or Update
. Because of this, OnSave
and PostSave
event handlers for these tables will not work.
Related article
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기