RobWhite_IV
Qrew Trainee
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: REST API - doQuery - get record ids
Thanks. I agree. I hope that doesn't become the case, because I'd hate to enforce an 'all-fields' default table view for my 'no(low)-code' QuickBase users. They generally don't care about recordId's, createDates, and other low-level record indicators. My favorite part of this service is how approachable it is for the 'normals', while allowing the nerds to go ham! Time will tell. ;) ~Rob ------------------------------ "The" Rob White IV ------------------------------Re: REST API - doQuery - get record ids
Hey Doug! Sorry to bother you so much with all this. Thanks for engaging with me. I do need all the fields, due to my implementation of my data across a variety of non-quickbase programs that treat my quickbase instance more like a standard database, rather than a slick no-code solution. I don't want websites spamming the QuickBase API, so my process to date has been to pull the data down intermittently, format it for template consumption by a website across a variety of platforms, then display it to the user (or general public, depending on the case). This allows me to provide a variety of caching mechanisms that I control based upon need. Also, I get to normalize the output in a manner that is a bit easier to deal with than what is provided from the API. I'd hate to think I will have to run expensive transform functions on each route at some point. Anyhow, I'll come up with something. Here is an interesting tidbit I ran across during this thought experiment that I want to share. For what it is worth... Testing from the docs Quickbase API Portal I went to a table with only a few fields. 19 total. 14 in the default report. I ran the query with SELECT set to an empty array. I got 14 fields. However, for the 'why not' factor, I set the SELECT value to 'a'. and got... Seems 'a' still works. Whether intended or not, I dunno. Just FYI. Hopefully they'll let me know before they patch it and break my stuff. I'm going with 'a' for my use for now. :) Thanks again, ~Rob ------------------------------ "The" Rob White IV ------------------------------Search as you Type Field User Access
So, Something in my app has changed and I need to know why! This form has worked in the past and someone must have implemented something that has caused this break. I have a form that features a search as you type lookup field for a record in a related table. For some reason, some of my users do not have access to that field now when trying to add a new record in the child table. Did something change that would require new permissions or a permission change to allow access to these users? I don't even know what to show you all for an answer, but I'll start with a view of the form from an admin perspective and the 'slightly restricted' user role's perspective. ADMIN VIEW OTHER VIEW Can you help? I'm happy to provide additional info if you can instruct me on what would be helpful in troubleshooting this issue. Thanks in advance, ------------------------------ ~Rob ------------------------------
