Using image onload field in a report leads to the repeated execution of the javascript and thereby leads to incorrect output
Using image onload field in a report leads to the repeated execution of the javascript and thereby leads to incorrect output
Forum Discussion
My script uses API methods and some advanced Async/Await JavaScript capabilities built into modern version of browsers - there is no GUI or page loads other than the final document.location.reload(true).
Using the <ask the user> feature and the associated URL parameters &nv and &v0 is not using script or API methods but rather loading new pages and using redirection features built into early versions of QuickBase during the Jurassic Epoch (ie dinosaurs). Continuing to use these archaic methods will hold you and everyone else back. The same goes for using &rdr in formulas URL.
The reason is simple: Using redirection methods to (1) chain together formula calculations or (2) step through workflow disturbs the entire application because the page reloads.
If you need to solicit user input prior to running a script use a dialog. as demonstrated here:
https://haversineconsulting.quickbase.com/db/bkw2ff3e3?a=q&qid=1
What is the Hylo Technique?
https://community.quickbase.com/quickbase/topics/what-is-the-hylo-technique
THIS IS NOT A TRIVIAL OR A PEDANTIC MATTER ON MY PART. THE USE OF REDIRECTION METHODS TO CHAIN TOGETHER URL FORMULAS OR TO FORCE WORKFLOW STEP EVALUATIONS WILL CONTINUE TO HOLD BACK THE EVOLUTION OF QUICKBASE AND IS PROBABLY ONE OF THE TECHNICAL REASONS QUICKBASE DID A REBOOT OF THEIR PRODUCT DEVELOPMENT STRATEGY.
STOP USING &rdr, &nexturl, &RedirectURL, &rl PARAMETERS AND 302 REDIRECTS
Using the <ask the user> feature and the associated URL parameters &nv and &v0 is not using script or API methods but rather loading new pages and using redirection features built into early versions of QuickBase during the Jurassic Epoch (ie dinosaurs). Continuing to use these archaic methods will hold you and everyone else back. The same goes for using &rdr in formulas URL.
The reason is simple: Using redirection methods to (1) chain together formula calculations or (2) step through workflow disturbs the entire application because the page reloads.
If you need to solicit user input prior to running a script use a dialog. as demonstrated here:
https://haversineconsulting.quickbase.com/db/bkw2ff3e3?a=q&qid=1
What is the Hylo Technique?
https://community.quickbase.com/quickbase/topics/what-is-the-hylo-technique
THIS IS NOT A TRIVIAL OR A PEDANTIC MATTER ON MY PART. THE USE OF REDIRECTION METHODS TO CHAIN TOGETHER URL FORMULAS OR TO FORCE WORKFLOW STEP EVALUATIONS WILL CONTINUE TO HOLD BACK THE EVOLUTION OF QUICKBASE AND IS PROBABLY ONE OF THE TECHNICAL REASONS QUICKBASE DID A REBOOT OF THEIR PRODUCT DEVELOPMENT STRATEGY.
STOP USING &rdr, &nexturl, &RedirectURL, &rl PARAMETERS AND 302 REDIRECTS