But this is easy to do with script and IOL:
Here is a screenshot of me manually applying a three line script
var urlParams = new URLSearchParams(window.location.search);
_fid_6.value = urlParams.get('_fid_6');
_fid_7.value = urlParams.get('_fid_7');
So the IOL
module.js code page would be this simple script:
(function(){
var querystring=document.location.search;
if(/a=er/i.test(querystring)) {
var urlParams = new URLSearchParams(window.location.search);
_fid_6.value = urlParams.get('_fid_6');
_fid_7.value = urlParams.get('_fid_7');
}
})();
This is actually a perfect example of my JavaScript rant yesterday which was probably over most user's heads but is simple to understand in this instance.
JavaScript keeps getting better every day. Now there is
(1) a new object available named
URLSearchParams that will allow you to manipulate the URL's query parameters and
(2) the browser automatically creates globals for all element ids in the page (ie
_fid_6 and
_fid_7).
You will
not see
URLSearchParams anywhere in QuickBase's code base but you will find various legacy code fragments that does the same thing. It isn't QuickBase's fault - every software company experiences this problem as the technology is changing too fast for even senior developers to keep up. Quite frankly I would be surprised if many QuickBase developers even know about these two particular features. Except that cute one - she seems like she knows her stuff.