Hello,
We are using the implicitSaveOnBlur feature with our DynamicForms. The data sources that the forms use have sparseUpdates set to true, so that when a user tabs out of a field after editing, just that field plus the primary key are sent back to the server as part of the save. This is working great.
We're getting stuck on the return. It appears that the DynamicForm is expecting a full record back after the save, meaning - every field represented in the return JSON, regardless of there having been just a single field saved because of the blur event. The issue we're having is that the user is often in the middle of editing the next field when the return from the server arrives and the edit values are overwritten with the data that came back from the server.
We've tried simply not returning data for fields that weren't saved, but then the form just wipes those fields out and they become blank. So either way the user is losing their edit values on fields they've moved onto when the save for a previous field returns. For now, we're telling people to wait for each field to completely save before editing the next... but obviously that isn't ideal and eliminates much of the convenience we were going for with the implicit save in the first place.
Is there an approach to this that we should try - or a property we're missing? Basically we just want the form to save the one field that caused the blur and then only update that one field on the return instead of the whole form.
We are using SmartClient v10.0p_2015-12-02/Pro.
Thanks much,
Philip
We are using the implicitSaveOnBlur feature with our DynamicForms. The data sources that the forms use have sparseUpdates set to true, so that when a user tabs out of a field after editing, just that field plus the primary key are sent back to the server as part of the save. This is working great.
We're getting stuck on the return. It appears that the DynamicForm is expecting a full record back after the save, meaning - every field represented in the return JSON, regardless of there having been just a single field saved because of the blur event. The issue we're having is that the user is often in the middle of editing the next field when the return from the server arrives and the edit values are overwritten with the data that came back from the server.
We've tried simply not returning data for fields that weren't saved, but then the form just wipes those fields out and they become blank. So either way the user is losing their edit values on fields they've moved onto when the save for a previous field returns. For now, we're telling people to wait for each field to completely save before editing the next... but obviously that isn't ideal and eliminates much of the convenience we were going for with the implicit save in the first place.
Is there an approach to this that we should try - or a property we're missing? Basically we just want the form to save the one field that caused the blur and then only update that one field on the return instead of the whole form.
We are using SmartClient v10.0p_2015-12-02/Pro.
Thanks much,
Philip
Comment