Forum Discussion
_anomDiebolt_
8 years agoQrew Elite
This is easy to do with a Service Worker. You can arrange for a Service Worker to detect when a particular pattern of URL is requested and take the appropriate action. In the case of Save as spreadsheet a URL is fetched that has the following query string:
?a=q&qid=1&dlta=xs~
Although a Service Worker has the ability to (1) modify or (2) substitute either the request or response in this case we will do neither and simply make a supplemental call to API_AddRecord recording the dbid and qid to a logging table. It is a ridiculously simple script to do what you ask.
There seems to be a lot of confusion, fear and loathing over the role of using Service Workers with QuickBase. The best minds in the industry have contributed to the development of the Service Workers API and they are safe to use and extremely useful. Developers are simply unaccustomed to using Service Workers as the capability has never existed before so they have no similar experience to draw on.
All browsers have support for the Service Worker API at this point (Apple is the last holdout but has support in Safari 11.1) and the Service Worker API has been adopted by several cloud service companies as part of their Edge Computing initiatives. This includes Cloudflare where they have adopted the Service Worker API and named it CloudFlare Worker which operate at the edge.
Cloudflare Workers
Run code at the edge, deliver powerful web extensibility
https://www.cloudflare.com/products/cloudflare-workers/
?a=q&qid=1&dlta=xs~
Although a Service Worker has the ability to (1) modify or (2) substitute either the request or response in this case we will do neither and simply make a supplemental call to API_AddRecord recording the dbid and qid to a logging table. It is a ridiculously simple script to do what you ask.
There seems to be a lot of confusion, fear and loathing over the role of using Service Workers with QuickBase. The best minds in the industry have contributed to the development of the Service Workers API and they are safe to use and extremely useful. Developers are simply unaccustomed to using Service Workers as the capability has never existed before so they have no similar experience to draw on.
All browsers have support for the Service Worker API at this point (Apple is the last holdout but has support in Safari 11.1) and the Service Worker API has been adopted by several cloud service companies as part of their Edge Computing initiatives. This includes Cloudflare where they have adopted the Service Worker API and named it CloudFlare Worker which operate at the edge.
Cloudflare Workers
Run code at the edge, deliver powerful web extensibility
https://www.cloudflare.com/products/cloudflare-workers/