ContributionsMost RecentMost LikesSolutionsCan you use a usertoken to download a file?The Quickbase Help does not include this information. https://help.quickbase.com/api-guide/index.html#filemanagement.html?Highlight=file%20attachments I was wondering if anybody has tried using the File API with a user token. Does it work?Re: Using Table Aliases in the URLsI have seen posts where developers recommend making an application level API_GetSchema to get the mapping of table aliases to dbids. The URL formatI describe would make this call not necessary anymore. As you said, I think the format form is usable when making copies of an application. In some cases, it is important to have a separate application for development from production. Assuming the table aliases match between DEV and PROD, this url format provides one less change to me made during the release to production. If a developer is also meticulous enough to keep the field IDs the same, the only change required for the release is simply to change the app DBID for these urls. For formulas, you can simply use the table alias in place of the table DBID, so this URL format would not be required. I don't see any limitations of using this URL format, however it does make it important to be descriptive when first naming the table. Since the table alias is generated based on the first name of the table and cannot be changed, (even by support, I checked), it is important to not have your table alias be _DBID_TABLE_1. To your final comment, watch the network traffic when visiting the MyQB page. There is some request madetohttps://intuitcorp.quickbase.com/db/bh28u4xv2/(_DBID_PUBLISHED)in all accounts. The call has to do with the Quickbase Marketplace.Re: Using Table Aliases in the URLsType it into the address bar. Try it! Here's an example: https://davidsbakery.quickbase.com/db/bfhqnt2n2/(_DBID_CUSTOMERS)?a=td bfhqnt2n2 is my app id _DBID_CUSTOMERS is my table alias I know its weird to have both the app id and the table alias, but consider that the table alias is defined by the original name of the table and that two separate applications can both have the a table with the same table alias. So the app id is required.Re: can we use table aliases in scripts filesOh I just posted on this. Yes you can as long as you have the app dbid. https://community.quickbase.com/quickbase/topics/using-table-aliases-in-the-urlsUsing Table Aliases in the URLsHi Everyone. I just discovered that you can use table aliases instead of table dbids to access tables. Like this: https://<your quickbase domain>/db/<app dbid>/(<table alias>)?a=td The table alias is case insensitive but must be wrapped in parenthesis. This works with apis too. Bye Everyone.Re: She's a Rainbowhttps://assets.quickbasecdn.net/res/873e615-1340/css/themes/classic/nav.css Your reference to the CSS file is going to break when Quickbase updates their repository.873e615-1340changes to something else periodically. You can get around this by replacing the firstpart of the urlwith Quickbase's global JS variablegResDir. Only issue then is that the service workers will execute before that variable loads. If only there was a way for service worker to cache that variable from the previous page load. Hmm...Re: React JS Library on Quickbase DashboardI know it's late, but this might be what you're looking for: https://community.quickbase.com/quickbase/topics/react-js-in-quick-baseReact.js in Quick BaseHello All, I want to share with you a technique to get your JSX React apps in a Quickbase dbpage. First, here's the challenge, most people are accustomed to using JSX with React, but JSX is not native JavaScript and must first be transpiled to JavaScript. This is easily accomplished in a server environment, but how to do this in a dbpage? The requirement came to me to find a way to make this work without using a server. The solution is to do transpiling on page load. This is slower than pretranspiling, but is ultimately necessary if you don't want to use a server. The alternative would be to upload your transpiled code, which you should definitely do if performance is a concern. By the way, performance impact for transpiling on load is negligible for small JSX files. Anyways, here goes: <head> <script src="https://unpkg.com/babel-standalone@latest/babel.min.js"></script>; <script src="https://unpkg.com/react@latest/umd/react.development.js"></script>; <script src="https://unpkg.com/react-dom@latest/umd/react-dom.development.js"></script>; </head> <body> <script type="text/babel" data-presets="es2017,react,stage-0" data-plugins="transform-decorators-legacy"> (() => { "use strict"; class Hello extends React.Component { render() { return <div>Hello {this.props.name}</div>; } } ReactDOM.render( <Hello name='World' />, document.getElementById('container') ); })(); </script> <div id="container"> <!-- This element's contents will be replaced with your component. --> </div> </body> Note that I am importing babel. Babel will handle the transpiling for scripts tagged with text/babel. What is in the script tag above is JSX, not native JavaScript. Copy and paste this code as-is into a dbpage. It should work without any modification. Now you can enjoyentering the world of React. Happy travels! David Maskasky