JenniferMarque1
Qrew Trainee
Joined 4 years ago
User Profile
User Widgets
Contributions
Re: Raffle Entry for Pipelines Qrew Meet Up May 14th, 2025
This was a really helpful presentation. I've used Postman somewhat, but am just getting into translating that to a pipeline. Authentication is where I've had the most problems. Does anyone have any tips on that? It seems like the API documentation for the various websites can be pretty difficult to understand. How do you know the best method to choose (if various options are available)? And how do you translate that to the pipeline? For instance, how did you know you needed to add "Authorization Bearer"? Anyway, got some really helpful tips and am looking forward to playing around.Re: Print Form to Landscape
We are using Exact Forms Plus - and it's great! However, that seems to work best for printing a single record on a form (maybe with a table of child records too). In this case I truly want to print a report. I think I said "form" in my reply, but I really meant printing a report. In this case I have a report embedded on a form. I could probably use Exact Forms Plus to do it, but it does seem like QB should be able to handle printing reports in landscape, even if it's an embedded report. Jennifer Marquette R.E. Pedrotti Company, Inc. Instrumentation, Controls, and System Integration 5855 Beverly Ave, Suite A / Mission, KS 66202 o: 913-677-3366 jenniferm@repedrotti.com / www.repedrotti.comRe: Print Form to Landscape
There are several older threads re. printing forms in landscape orientation. I was facing this exact same issue and wasn't finding any answers here. So I did some further digging/general Googling, and here is what I found. Apparently (at least with Chrome), having "an @page size declaration in the print CSS will override (and hide) the orientation on the print dialog." This is from this thread on Stack Overflow. I took a look at the CSS for the print window that opens when you select to print a form. Sure enough, there is an @page{size: 8.5in 11in;} declaration in the <style> section. I'm not sure why they would put that in there; does it just default that way for the US? What if you wanted to print on legal paper? However, the "solution" in the above referenced Stack Overflow thread, installing the Stylus extension, actually did work. I just created a new style with @page{size: auto;} and applied it to Everything and it worked! That extension is for Chrome; not sure if there is something similar for other browsers. The only issue is that I'll need to install the extension for all users that need the ability to print landscape. I may reach out to support to find out why they put that letter-size @page declaration in there at all. ------------------------------ Jennifer Marquette ------------------------------Re: Growing frustration over mobile bugs
You are not alone! I have quite a few bugs in the mobile app; most, but not all, are related to dynamic form rules. It makes it very difficult to roll out changes to our main app. I have it tested and working just fine in the browser; then when I test on mobile it doesn't work properly. Sometimes I can ignore or work around, but not always; right now I have a change that I have to delay because it won't work correctly on mobile. It's frustrating to have to change directions just to work around mobile bugs! I have brought some of the issues up with my QB tech consultant; his response is always to submit to support, which I get. Unfortunately, I know the best way to make sure it is moved up the chain quickly is to provide lots of detail and, ideally, a video. That of course takes time to do. Some of these issues are very basic (a DFR that changes the value of a field when another checkbox field changes); it's hard to believe that no one else has discovered this before. I have to assume it's just not a very high priority. ------------------------------ Jennifer Marquette ------------------------------Re: Powerapps vs Smartsheet vs Quickbase
I know this is an older thread, but thought I'd post in case someone else comes across it and is curious. I am a relatively new Quickbase user; we have also been using Smartsheet for a little over a year. The biggest difference for me is that QB is a relational database; Smartsheet is not. You can do cross-sheet lookups (via a formula), but no record picker functionality. Also, the Smartsheet forms are somewhat limited. There are definitely some things I like about Smartsheet; for certain things it is easier to accomplish than in QB. I'd say for the average non-technical user, Smartsheet is easier to pick up on. It is much more like Excel, although with much enhanced capabilities in certain areas. Sounds like Power Apps is on one end of the spectrum, Smartsheet on the other, and QB in the middle. We are going to continue to use SS for some functions. I come from a database development/programming background; I am working on an app now that definitely needs the relational database capabilities of QB. I had originally hoped to develop it in Smartsheet but quickly realized it wasn't going to work. One advantage of Smartsheet is that you don't need a paid license for users to access your "apps"; they can add data and make changes with just a free license. You only need a paid license for anyone who is going to create workspaces/sheets (the SS version of apps & tables). ------------------------------ Jennifer Marquette ------------------------------
Groups
App Builder Qrew
Are you a builder? This Qrew is for you. Come discuss all topics builder focused here.Construction Qrew
Where Qrew Members within Construction can meet and discuss industry challenges.Mobile Qrew
For your mobile based use cases, there's no better space to discuss Quickbase mobile than in the Mobile Qrew.Pipelines Qrew
A Qrew dedicated to sharing all things Pipelines.Realm Admin Qrew
Where Realm Admins help other Realm Admins Realm Admin.
