Forum Discussion
_anomDiebolt_
9 years agoQrew Elite
I updated my answer where I wrote "adjacent sibling selector +" where I should have wrote "adjacent sibling combinator +".
In any event, creating your own Save button might not give you all the functionality of the real save button. There are a number of things the QuickBase Save button does behind the scenes that may not be apparent such as conflict resolution or field validation. So even if you Save button appears to work now for simple cases you might get a different behavior with one of the edge cases.
When I modify the behavior of a QuickBase form I try to make the least invasive change to the page. Often time this is done through writing script that either automatically creates or intercepts a user action. You can think of such a script as as acting like an "invisible friend" that is generating user input on your behalf through script. In this fashion you script will not interfere with QuickBase code.
In any event, creating your own Save button might not give you all the functionality of the real save button. There are a number of things the QuickBase Save button does behind the scenes that may not be apparent such as conflict resolution or field validation. So even if you Save button appears to work now for simple cases you might get a different behavior with one of the edge cases.
When I modify the behavior of a QuickBase form I try to make the least invasive change to the page. Often time this is done through writing script that either automatically creates or intercepts a user action. You can think of such a script as as acting like an "invisible friend" that is generating user input on your behalf through script. In this fashion you script will not interfere with QuickBase code.