Using Table Aliases in the URLs
Hi 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...
Forum Discussion
I have seen posts where developers recommend making an application level API_GetSchema to get the mapping of table aliases to dbids. The URL format I 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 made to https://intuitcorp.quickbase.com/db/bh28u4xv2/(_DBID_PUBLISHED) in all accounts. The call has to do with the Quickbase Marketplace.
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 made to https://intuitcorp.quickbase.com/db/bh28u4xv2/(_DBID_PUBLISHED) in all accounts. The call has to do with the Quickbase Marketplace.
