Changes between Initial Version and Version 1 of Ticket #30937, comment 83
- Timestamp:
- 10/24/2016 06:53:56 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30937, comment 83
initial v1 2 2 3 3 OK thanks got it. The solution in my case will be to override the `api.previewer.query` method only in a refresh case, to always post the full set of customized values (and not only the ones not yet saved in the DB changeset) 4 The new utility `api.dirtyValues()` with `{ unsaved : false }` as paramwill be my friend.4 The new utility `api.dirtyValues()`, with `{ unsaved : false }` as param, will be my friend. 5 5 6 6 > Feel free to ping me on #core-customize in Slack to chat about this further as it's probably a better place to discuss your use case.