The URL shows something like this …
If the user presses save twice the save process gets interupted and starts working on the remaining values in the metadata. What you might want to do is to set an additional action on the custom save that will update a Ui only field to true and then disable the Save button based on the true value. This should stop the users from pressing the save button twice. The other method, and probably the best one, would be to use multiple actions on your save button and block the Ui (with a message Saving…) until the save is complete and then unblock the Ui after.
Hi Gregg, thanks for you response and I have resolved the issue with the Blocking UI feature. But Still I have question in my mind that why user is allowed to click two times on Save button ?
Ideally once the Save is clicked, User shouldn’t be able to click it again, but this is something strange what I have seen on Save button. Another thing is what exaclty is Clone_1 which got appended in the ID in the URl ?
your inputs will be highly appreciated.
The Save button is an independent component and is customisable. To make it not active after a single execution would be limiting to some other type of functionality that it could be used for.
Clone_1 is the Salesforce backend code that generates this extension. You can use multiple actions in Skuid and when you save the record you have the opportunity to use your own naming conventions.