Pinned Discussions
Forum Widgets
Recent Discussions
YTD Reporting-Best Practices
Hello! I am working on a monthly and yearly sales report and I have run into a hiccup. Scenario: I have a record that is a booking ("sale") that is made in Jan 2025 and then in Mar 2025 the booking is cancelled. The way I have it now is that when the booking is made, the status field changes from quote to booking and then when cancelled, the same field changes to cancelled. In my YTD report, this is causing the booking made in Jan 2025 to not show up due to the cancel in Mar 2025. I understand it is a wash, but I still need the booking to show up in Jan 2025 and then the cancel show in Mar 2025. So, this is what I am thinking for a solution: Create a date field unrelated to the status field that will populate when a cancel occurs and have the report pull of the booking date/status and also from the cancel date report and that should then show both transactions OR create a separate table that will hold the numbers at month end for each month and pull the YTD report from that table? I would just like any input/advice from someone more knowledgeable than myself. I am hoping I am thinking about this in the right way. Thank you, Kim0likes0CommentsNeed help deciding between two db setups
I am pretty new to qb and am currently trying to create an app to help my department track a student's requested thesis committee. The (hopeful) process: student will submit form with their identifying info, proposed thesis title, then choose their requested thesis supervisor, and selected reader, both fields pull from the same list of faculty (though if someone is chosen in one field they will not appear in list in 2nd field - that's for another time to figure out). So in trying to build something I came up with two different setups and am wondering which people think would be best. Which do you think will be better longterm. Attached are screenshots of both relationship diagrams. Hopefully they are decipherable.0likes7CommentsHow can I avoid saving a form if I need the user to create another record in a related table first?
Hi I need support with the following issue, I have created a form. This form contains a button to add more product requests. But many times users do not add products to the request and the request remains open and empty, unattended and incomplete. Until the user comes to upload products and in the form selects that no more products need to be added, Quickbase executes rules and notifications to complete this multiple or single product order as completed and processes the request. The problem is that I don't know of a way to prevent them from creating and saving the empty product order. Is there any way to achieve that result?0likes4CommentsMandatory Multiple Attachment for a Record
Hi, I have a use case where I have to attach the multiple attachment for a record and if the attachment is not attached then it should not allowed user to save the record. However, I have created a separate table for storing attachments and formula url button in parent table which redirects the user to the child table to create the record for Attachment and created dynamic form rule if Attachment required =yes and #of Attachment =0 abort save. But the issue is if user have provided all the details and missed to attach the attachment it is not allowing user to redirect to another page for adding attachment without saving the record and record cannot be saved because user has missed the attachment and if user wants to attach attachment they have to refresh the page first which results in loosing all the data which user has filled in the form. If I change the URL properties to popup window then also attachment will not be visible until user refresh the page. Kindly suggest the better way to add multiple attachment for a record, even user missed the attachment it should not allowed them to save and let them add attachment without refreshing the page. Thanks0likes0CommentsHow to manage HTTP "accounts" in Pipelines
I'm using the HTTP "Make Request" step in several pipelines to make HTTP calls from Quickbase to my applications API. The way you configure the URL and authentication information for that API is via the "Connection" where you configure an "HTTP account". I can see how to create a new "account" there, but I can't figure out where to update or delete those accounts. I've searched the Quickbase UI and couldn't find anything, and the docs didn't contain anything that I could find. I considered using "variables" to try to specify my URL and reference the variable in the "HTTP account", but that context doesn't seem to support variables, which seem like they were built for use in formulas, not pipelines. Can anyone tell me how to manage (edit, delete) my HTTP accounts used in my pipelines? Thanks!0likes0CommentsEmbedded Grid Edit Report Pre-filtered Conditional Dropdown
I'm trying to get an embedded (report link) Grid Edit report field to return a pre-filtered conditional dropdown list similar to how a Form field can filter based on a report. This is a Legacy Form. In screen shot 1 one can see a conditional dropdown list of Standard Deliverables (conditional on Discipline) that filters out Obsolete (checkbox field) deliverables by using the Form's "When Used for data entry:" filtered dropdown report. (filtered Obsolete not equal checked) I'm trying to replicate this behavior in an Embedded Grid Edit report, however, the full list of deliverables including the obsolete deliverables are showing up (eg. 3300 Utilities and 3610 Fabrication Drawings) and there doesn't seem to be an obvious method to pre-filter this dropdown list (ie. pre-filtered report). I've done some reading on the subject in these discussions and the following discussion seems closest (https://community.quickbase.com/discussions/quickbase-discussions/embedded-grid-edit-report-help/18372), however, I haven't been able to get any of these ideas to work. Any help would be appreciated. Please let me know if additional information is required. Screen shot 1 - Individual Record Form Conditional Drop Down List Screen Shot 2 - Grid Edit conditional drop-down Thanks in advance for any help!Solved0likes15CommentsValidation error: Incorrect template "{{c.user.id}}". ValueError: invalid literal for int() with base 10: 'user'
I am not sure why I am getting this error in my pipeline. invalid literal for int() with base 10: 'user' ------------------------------ Melanie Proebstel ------------------------------1like3CommentsHow to display clickable links from two separate tables under one field
I have an app with the following setup. IVRT and ARHIFU are parent tables. All Patients is the child table. In All Patients, I have lookup fields pulling in patient name report link fields from both the IVRT and ARHIFU tables: [IVRT Patient Name Link] (from IVRT) [ARHIFU Patient Name Link] (from ARHIFU) These lookup fields correctly show the patient names as clickable links in the All Patients table. Now, I would like to display the clickable links from both of these parent tables under one field in the All Patients table. (See attachment). The problem I am running into is keeping them as clickable links. How can I display the clickable links from both parent tables under one field in All Patients? If a formula is needed to achieve this, what would that formula look like? Thank you! Meagan0likes3CommentsHelp with Lookup Fields from Multiple Parent Tables in Quickbase Form
Hello, I have a Quickbase app where a single child table is connected to three separate parent tables. Each parent table represents a different employee group, and the child table is set up to pull employee information from all three. In the form for the child table, I want to be able to look up and select employees from any of the three parent tables. However, I can only select from the first parent table I connected—its lookup field is active. The lookup fields for the other two parent tables appear grayed out and are not selectable, even though they are all connected in the same way, using the employee name as a lookup field. As shown in the screenshot, only the first table’s name field is selectable, while the others are disabled. What might be causing this behavior, and how can I make all three lookup fields usable in the form? Thank you!Solved0likes3Comments