Workaround for 20 Option Max in Multi-Select Text field?
I found this thread from years ago (https://community.quickbase.com/discussions/quickbase-discussions/multi-select-fields-max-100/76382) that demos a really clever method to get around QB's limit of 100 options in a multi-select text field, but I have sort of the opposite issue where I have a multi-select text field that contains a list of all 50 states, and I want users to be able to select potentially up to all 50 options, but currently they're limited to 20. There are a handful of workarounds (breaking the states list into multiple fields, creating 50 individual checkboxes for each state, setting up a sub-table with an embedded grid report on the form where the user would create 1 record/state), but none of those options are nearly as elegant/intuitive/UX friendly as just a single multi-select that lets you pick more than 20 options. Anyone have any ideas? This is for a project where the intended users are external users who have 0 QB experience and would only ever fill out this form once and then be done, so it has to be really easy/intuitive; there won't be any time to train users on how to fill out a form using any of the other options I considered above. Thanks!Solved40Views0likes1CommentMobile Screen Jumping
I have a form that generates approximately 500-600 submissions per day. The form currently contains 320 fields, 55 form rules, 100 lookup fields, and around 80 image fields. I've been troubleshooting a significant issue on mobile devices where selecting any multiple-choice question causes the screen to jump erratically. To isolate the problem, I've tried: Removing all image fields Reducing the total field count Creating a simplified version with only 5-6 questions and roughly 30 fields Even with the stripped-down version, the screen jumping still occurs whenever a multiple-choice field is selected on mobile. Has anyone experienced something similar or have suggestions on what might be causing this? I'm trying to determine whether this is related to form configuration, form rules, lookup fields, browser behavior, device-specific issues, or a platform limitation/bug. Any troubleshooting ideas would be greatly appreciated.67Views0likes3CommentsHow to add Tabs (Pages) to only a specific section of a form?
Hi everyone, I’m trying to organize a form using Tabs (Pages), but I’m running into some confusion with how Quickbase handles them.Previously, I was able to add new sections below existing ones without issues. However, when I try to add a new Page (Tab), Quickbase automatically moves all my existing fields into Page 1 and puts the new fields on Page 2. The tabs also always appear at the very top of the form. What I actually want is to have tabs (or a tab-like experience) applied to only a specific section lower down in the form, without wrapping the entire form into multiple pages. Is there a way to achieve this? Or what is the recommended approach — using multiple Pages, Sections with rules, or a completely different method? Any advice or best practices would be greatly appreciated! Thanks in advance.51Views0likes3CommentsStrange Problem with a relationship and record picker.
I have a long standing table, Core Returns, that has a lot (too much, but just blame Admins long retired) of information. There is a field that gets filled in at a point well after the record is created, automatically, through updates. That part is working fine. I recently added another table, HVNE PO's, as part of a different project that does share some data with the older table. There is a reference to an 'Equipment' number. That number is the Primary key in the HVNE PO's table. I have it set where the HVNE PO's table is the parent table and Core Returns is the child table as that same equipment number can and does crop up in the Core Returns table multiple times. The Equipment number, however, does not necessarily exist in both places. The Goal is to allow a User to look from the Core Returns table and see if that Equipment number exists over in the HVNE PO's table. The users' decision about what to do next is impacted by this. So that's what I want. My Relationship is like this: HVNE PO's is Parent, Core Returns is Child. Equipment is the Text (Key Field) in HVNE PO's. Ret_Equipment is the Text (Reference). The reports display everything as expected. Now, in the form to look at records in the Core Return, when just looking, it displays as expected, but when you go to Edit the record, Ret_Equipment displays a date and gives a drop down with completely unrelated information. If I don't touch that field, make other changes that I need to make, when I return to the report or the eyeball view, it's fine. The problem is that I may occasionally need to edit that field and now it's all screwed up for that workflow. I have a gut feeling that it is a simple setting somewhere, but for the life of me I can't find it.55Views0likes3CommentsImport Field : Formatting Font
We use QuickBase to review changes to requirements. Is there a way to allow us to format font in a field without applying the code to the entire field contents? (as below?) I want to demonstrate be able to show the user what has changed in the requirement clearly. In the past we have been able to format the font in excel and import it into the database but that is no longer working, and of course there is no way to format the font manually I'm unsure how to format the font manually.87Views0likes5CommentsAdding child records that rely on lookups in new forms
I have a new-style form that displays pages as steps. The user clicks the button (Formula URL) under step #3 to add a child record. Once they save that record, they're redirected back to the form, but on step #1. How do I bring the user back to the last step they were on? URLRoot() & "db/" & [_DBID_TABLE_ALIAS_HERE] & "?a=API_GenAddRecordForm&_fid_6=" & URLEncode ([Record ID#])& "&z=" & Rurl() The app uses New Grid Reports. I tried having the user add records in-line, however those rely on lookups to the parent and they won't save, saying that the lookup value is not set. I created a new Formula URL button to redirect back to that specific tab. It works when editing/viewing records but not when adding. URLRoot() & "db/" & [_DBID_TABLE_ALIAS_HERE] & "?a=API_GenAddRecordForm&_fid_6=" & URLEncode ([Record ID#]) & "&NextURL=" & URLEncode(URLRoot() & "db/" & Dbid() & "/form?a=er&rid=" & [Record ID#] & "&page=2")Solved101Views1like4CommentsRequired Field Default Lookups SSN
how would i make a fake social security number when the data entry doesn't have it at the time? it would need to lookup in the SSN field for 999-99-9999 999-99-9998 999-99-9997 etc. and the next auto entry would be 999-99-9996. I could create a table with all the possible values or maybe there's a formula to use somehow?Solved56Views0likes2CommentsQR Codes
Trying to get a qr code to print on a 4x6 label and I am using Exact Forms Plus and I have the following formula in my purchase order table under QR Code: "<img src=\"https://quickchart.io/qr?&size=150x150&text=" & URLEncode(URLRoot() & "db/" & Dbid() & "?a=dr&rid=" & [Record ID#]) & "\" />" No matter how I have that formatted it does NOT change the size of the qr code as shown in the attached picture. Using that formula, the qr code does scan to the correct information. I had found a format on one of the help tutorials telling me that I needed to use this code in my template: ~=barcode(f[227],qrcode,150x150)~ When I use that field in my template, it works perfectly and I can get the qr code to resize just the way I need it to at whatever size, BUT The code no longer scans. It comes up to a google page searching for F(227).Solved184Views1like6Comments