Prevent save a record - New forms
Hi, I was wondering if anyone can figure out how to avoid saving a record with duplicate attachments. The scenario is as follows: I have created a new version form and added three fields attach type. These are mandatory. In legacy forms, this works partially because as I only validate that the name is not identical between the attach type fields. But quickbase has no validation at the level of the attachment field content level. Thinking outside of the box I have implemented the following dynamic formula to avoid saving, when these attachments are duplicates. But when I implement this dynamic rule in the new version of the form. it doesn't work.Solved83Views0likes8CommentsHow to add a link to new notifications?
Does anyone know how to add a link to new notifications? In old notifications you can simply make a rich text link and reference the field, but in the new notifications it just shows the rich text field as text. My use case is: The notification fires from a child record, but I want to be able to have a link to the parent record in the email.79Views1like2CommentsThe new "sidebar" navigation sucks.
The new "sidebar" navigation sucks. Everyone in my organization hates it. It is needlessly cumbersome to do anything now. It is also really stupid that you guys aren't going to let us, the paying customer, simply have the choice in how we prefer to use it and instead force it down our throats after the new year.Solved712Views8likes27CommentsNew Charts/Graphs/Dashboard
QuickBase However, the new gauge charts are NOT gauge charts and they don't show the categories like the current gauge charts show. There has to be an option to use "whichever" graphs desired (new and old) without forcing the user to pick from the old or the new.18Views0likes0CommentsDocument Template/Creation (PDF)
First off, loving the document/pdf creation function. Has opened some new areas of opportunity in a few tables. One thing I am having trouble with, maybe a setting/enablement I am overlooking , but I want to enable a user to generate a document from any given filtered view or a customized report view. For example I have material requests for various jobs, if I create a report to filter to just by job and visibly only see that job's requests, we'd want to a user to have the ability to just click generate a document and it makes it off that view's records. If I do that now, it actually generates the document for the whole overall table, not what report I'm in and what records I visibly see from that report.91Views0likes0CommentsSide Bar Navigation SUCKS.
Am I to understand that top navigation is going to be permanently moved to side navigation beginning in 2025? If so, that is one really dumb move. We have ALOT of reports that are designed to fit on the screen exactly as they are. Now they will all have a horizontal scroll bar which makes it an unnecessary waste of time having to scroll left to right to see the entire report. Why do you guys arbitrarily change stuff nobody really asked for? And why don't you just give us the option to stay with what we are comfortable with. Removing choices in preference is really stupid.179Views3likes3CommentsNew Navigation difficult on iPhone /iPads
I'm finding that collapsing the side bar on new navigation is difficult on Small mobile devices like iPhones and iPads. I'm looking for some upvotes on User Voice / Feedback to make sure the Product Managers consider those devices before they remove access to Top Navigation sometime in early 2025. https://feedback.quickbase.com/app/#/case/427172?currentProductId=3c9d7e83-da43-482e-a58c-14265037ecd038Views0likes1CommentThe New Pipeline Builder UI is a downgrade overall: Please adjust it
This will probably be a hot topic, but it needs to be said since the better legacy builder UI is being removed soon. Posting here rather than a "suggestion" because in my 6 years of doing QuickBase Development, the suggestions page has proven to be basically useless at getting the word out on issues. Overall the new PL Builder UI only offers ONE feature that is a benefit, which is full step-reordering. But, this should have just been added to the old UI. Who asked for a new UI? The new UI, overall, is just cumbersome/slow and annoying to use. I have waited for a long time now, expecting the UI to be improved, but I've see no such fixes to the issues the new UI has, as such it is now time to talk about it. See my images below with added notes. Below is probably one of the absolute worse design choices overall; Why do we have to OPEN each section of the step? What value does this add? All this does is slow down the process by forcing me to go "open, open, open" when in the old one I can see ALL THREE items at once. The old view is beyond better: Open the step, take a glance, bam, done. This adds literally ZERO benefit to admins/devs. The old UI has too much white-space, but at least I can see everything.58Views1like2Comments