Formula URL button - save and redirect
Hi there I?ve created a form accessible to ?everyone on the internet? for our clients to submit service requests. I added ?&ifv=20? to the url to hide the qb branding. However, doing this causes the save button to become hidden. I created a formula url button that will save it using this javascript I found on the forum: var text URL = "javascript:void(DoSaveAdd())";var Text Image = "<a id='saveButton' class='Vibrant Success' onclick='DoSaveAdd()' href='#'>Submit</a>";"<b href =" & $URL &">" & $Image & "</b>" My problem now is how do I get the page to redirect after the form is saved. Here?s a link to the form, you can try it and see what happens. https://sparkav.quickbase.com/db/bnzwm7ykp?a=nwr&ifv=20 I'd like it to redirect to an external webpage. If that is not natively possible than I'd like it to redirect to a rich text page I've created in quickbase. Any help with this would be greatly appreciated! Thanks, ElishaForm(s) on Home Page
I can't be the only one who is needing this, and maybe it is so simple that it is just too dumb to have on the forum, but I also have had a struggle looking through basic help on this. I would like to put an intake form, maybe even two forms, directly on the home page. Like bam! first thing. No click a button to go to a table. Just form first thing. I would like it to just say Thanks or can even go to a report or something afterwards, but I can get to that later. Again, simplest solution to the problem is best. This is not an open to the internet solution, but could be later. Swift help would be awesome. (I also wanted to put this out here so that others could have a solution as well)
How to display PDF in file attachment fields
File attachment fields can show the attached files in forms and reports, but only a few file types are accepted (jpeg and such). Is there a way around this so that PDF attachments can be shown either directly in the form, or as a pop up window (I believe that is called an Iframe ?) after clicking on some button for that purpose? I now have that sort of working through a Chrome extension, which opens the PDF in another tab, but it's slow and cumbersome and has some unwanted side effects.
The Jan 21st UI Update
The Jan 21st UI Update is awful. Our company uses many forms that span without having to scroll horizontally. We now have a bunch of forms that are scrolled off the screen. Terrible. Please give us the option to go back the the basic "blue". We did not ask for this update, nor did we want it.
Is it possible to create a ""Save and Keep Working"" button from a formula URL field?
I realize the "Save and Keep Working" button was introduced by Quickbase, but I am wanting to add it somewhere in the middle of my form. I've seen posts relating to this kind of thing, but all of theme were published prior to the introduction of the "Save and Keep Working Button" and I can't seem to get any of them to work. Any thoughts?
Add a button to open a specific form?
I have a table that everyone has access to. Lets call it "Products". For the purposes of this discussion, every role has the same access. I want to be able to add products through two separate buttons on the home page. The first is already there. It takes us to our current add form. We want to keep this. The second, is not. Right now we have it set up on the current add form through dynamic form rules, but you have to answer about 3 different drop downs before you get to it and it is confusing to users. What I want is to have a second button, that when clicked, takes you to a different form I have created to add these specific products. It would be the same for every role. Is this possible, without setting form rules with the roles? Every role would need access to both. ------------------------------ mtn mtn ------------------------------New Forms Are Now Live in Quickbase Mobile!
We’re excited to share that as of April 21, the new forms experience in Quickbase is now generally available on mobile! This launch marks a significant milestone in our mission to provide a seamless, consistent, and powerful experience to users—no matter where they work or what device they use. Why This Matters Historically, building for mobile in Quickbase presented a number of challenges. App Admins often had to create and manage separate legacy mobile forms to provide a usable experience on smaller screens. For end users, the experience was often inconsistent. Legacy mobile forms came with limited layout options, lacking the flexibility to organize content using columns, or tabs. Form rules and workflows sometimes behaved differently than expected, and key functionality—like viewing embedded reports directly on the form—wasn’t available on mobile at all. As a result, mobile usage often required workarounds, compromises, or shifting tasks to desktop, slowing down teams who needed to work when they were away from the desk— until now. One Form, Multiple Devices The new forms experience is now fully responsive. Builders can design a single form that automatically adapts to desktop, tablet, or mobile, with no extra configuration required. Whether users are approving invoices, pulling up customer contacts, submitting support cases, or updating project details, the experience is consistent and intuitive across the board. What’s New for Mobile Here are a few key enhancements you’ll notice right away: 🔹 Fully Responsive Form Canvas The layout automatically adjusts to the screen size and orientation, while maintaining the structure and design you built on desktop. Forms are organized with pages, sections, columns, tabs, and steps, and Quickbase automatically adapts the layout to fit the device's screen. For instance, on mobile devices, columns stack vertically to ensure optimal readability and usability. On tablets—especially in landscape mode—forms can display multiple columns side by side, taking full advantage of the larger screen and offering a more spacious, desktop-like layout. Additionally, tabs and steps help break down longer forms into manageable sections, making it easier for mobile users to navigate complex forms without feeling overwhelmed. Users can quickly swipe through form steps or tap between tabs, maintaining focus while completing tasks efficiently. 🔹 Optimized Field Interactions We’ve reimagined how field components work on mobile. From dropdowns to date pickers, every interaction is optimized to feel natural on a smaller screen, while retaining the power of the desktop version. For example, multiple-choice fields are presented in modals, allowing users to search and select options efficiently. 🔹 Dynamic Form Rules & Workflows Form rules and formulas now behave just as they do on desktop. We’ve been on a mission to eliminate the need for mobile-specific workarounds, and this update is a step forward. Dynamic form rules now apply across devices, so the logic you’ve built for desktop users works just as smoothly for those on the go. 🔹 Embedded Reports on Mobile For the first time, embedded reports are displayed directly on mobile forms, giving users real-time access to the related data they need to make decisions and take action on the go. While some functionalities like grid edit and exporting to CSV are not supported on mobile, users can view reports, search, add new records, edit or view individual records, and delete records, depending on their permissions. 🔹 Support for Custom Workflows New forms on mobile now support more advanced and flexible workflows. App admins can confidently use table-level settings like “Auto save when redirected away”, the custom CSS class SaveBeforeNavigating, and URL parameters such as ifv=1 and hs=1 to hide native Save and Cancel buttons. These tools enable customized navigation, smoother inline saves, and fully tailored form experiences—all while maintaining mobile compatibility. Assigning Forms for Mobile App admins can assign the latest, mobile-friendly version of forms to specific user roles using the "View/Edit/Add Form (Mobile)" column from Forms Settings, ensuring that users see the appropriate form on their mobile device. In some cases, assigning a simplified, mobile-specific form may be beneficial. It allows you to reduce friction, minimize cognitive load, and create a faster, more focused experience for users – especially for those who only need to complete a subset of fields or perform quick tasks on the go. Alternatively, if admins prefer to use the same forms across desktop and mobile, they can select “Use full site forms”. A Better Experience for Builders and End Users With this release, builders no longer need to build two versions of a form, and end users don’t have to adapt to a stripped-down mobile layout. The result? Faster time to value and more efficient teams. Ready to Get Started? If you’re already using new forms on desktop and you have selected the option “Use full site forms” for mobile, you don’t have to lift a finger—your mobile experience is ready to go. Just open your app in the Quickbase mobile app (version 1.68 and above) or browser and experience it for yourself. If you’re not using new forms on desktop yet, now is the perfect time to start. By switching to new forms, you’ll not only unlock a modern, flexible form-building experience on desktop—you’ll also ensure your app is mobile-ready. 💡 Want to learn more? Check out the full documentation: Assign forms for mobile Understand the form canvas and layout on mobile Form field types and components on mobile What’s Next The launch of new forms on mobile is a big milestone—but we’re not done yet. In the coming months, we’ll be rolling out additional capabilities including: QR/Barcode scanning Next/Previous record navigation, making it easier to move between records Timezone helper, and more!
Username to text field
I am working on a way to log changes to specific fields. I have created a history field that records all the information I want to track when it is changed into an entry in that field. My problem is there are 2 user fields that have Full Name in them and when I attempt to pull than information out and into the new History field it only prints some id number associated with that user, I want it to print the Full Name of the User. My history field is a multiline text field. Below is the action to my dynamic form rule. It states: When the record is saved Action change history to <br><b>Status:</b> [Status] <br><b>Changed by:</b> [Changed by] | <b>Changed Date:</b> [Date Changed]<br><b>Tested By:</b> [Tested by] | <b>Tested Date:</b> [Tested Date]<br><br> Again, everything in this prints beautifully with the exception of the [Changed by] and the [Tested by]. Here is what an output would look like: -- [OCT-23-14 4:19 PM Jordan] -------------- Status: New Changed by: -58508613 | Changed Date: 10-23-2014 Tested By: -58082747 | Tested Date: 10-24-2014 Any guidance is greatly appreciated.
