If you’ve ever used JavaScript to modify UI or enable a non-native workflow in a Quickbase app, this post is for you. We know that adding custom code to an application can be a valuable way to extend...
Updated 10 months ago
Version 2.0
Blog Post
@Evan Martinez I utilize the API to develop custom reports (in the form of mini Vue WebApps) to deliver functionality not available in Quickbase reports. Even though pieces of the app are open to everyone on the internet, these reports (pages) should not be.
I was able to resolve this problem by swapping out user token authentication for temp token authentication using the new JSON API, as the temp token allows for the QB authentication credential to be passed along with the request. When a token cannot be generated (in the event of a not logged in user), the app knows to not make the data fetch call and display an error instead.
I was able to resolve this problem by swapping out user token authentication for temp token authentication using the new JSON API, as the temp token allows for the QB authentication credential to be passed along with the request. When a token cannot be generated (in the event of a not logged in user), the app knows to not make the data fetch call and display an error instead.