Changing Record Picker List Dynamically
Here's the situation: Table A is the parent to table B The reference lookup field's record picker in table B is based on Report1 from Table A There is also Report2 from Table A that the record picker can be based on Is it possible to have the record picker for the lookup change from Report1 to Report2 based on a checkbox (or some other kind of field) on the form for table B? I have tried to copy the look up field, rename it, change its record picker to Report2, and then use dynamic form rules to set which field is visible for the user based on a checkbox, but the result is both lookup fields are visible or hidden at the same time. I cannot figure out how to hide one and not the other. I, also, cannot figure out another way to create this setup, so users can see options to choose from based on Report1 or Report2, depending on whether or not a checkbox is checked. I hope this explanation was clear enough for someone to offer some suggestions / guidance. If more details are needed, let me know where you are not clear, and I will do what I can to fill in the gaps. Thanks in advance for any help anyone can give. ------------------------------ James Carr ------------------------------Solved40Views0likes7CommentsAirports related to hotels
Good afternoon, Still learning QB and I need help with conditional formatting. I have a list of airport codes and each airport has one hotel or multiple hotels related to that city. When an user selects the airport they want too, I want the hotel field to provide all the hotels related that city. I have been struggling with issue for a while now. Thank you for all the help.17Views0likes1CommentField completed auto populates other fields
I am new to developing in Quickbase or any other program. I am building an app where if a person selects one of three regions, I would like to populate only those associated with that region to select. For example, I have three regions, and each region has three items (each item is different in a region and stored in a region table), when I select Region X, I only what the three choices in Region X to be displayed, not the other items associated with the other two regions. Thoughts or suggestions? ------------------------------ Brent ------------------------------15Views0likes1Commentconditional dropdown
Hi, I'm trying to utilize conditional dropdowns and running into an issue that I can't figure out. Here's the relationships: Project Management App has Projects. Each Project has many Sign Types (think of these as Products associated with a Project). Production App syncs Projects. Each Project (sync table) has many Production Tasks. Production Managers Task via Production Tasks. They click on a button on the Project sync table in Production and it associates the Production Task with the Project (in the sync table) but I lookup the Record ID#2 (the original in PM app). Nothing unusual here. What we're looking to do is gain further granularity into how long each Production Task associated with a specific Product (each Project has anywhere from 1 to sometimes 100). So, I created a join table "PT Chains" in Productions to help with this many-to-many relationship. Production Tasks -> PT Chains <- Products. Utilized lookups to bring the related "project" from Products and Production Tasks has the "Record ID#2" which is the same ID in the Production App. I've tried to use Grid Edit and directly adding a new record into "PT Chains" but inside that table, if I enable "Conditional Values" and try to line-up the Record ID#2 and "Related Project" from Sign Types (first attachment) but it seems like this is entering into a circular relationship, where I think it should work. Production Manager creates a Production Task off of the related project. The "Add PT" is a normal Formula URL with the associated fields already filled, so it knows of the Record ID #2 field, which is the record id of the project. Then, as they're creating the task, they should be able to "add in" via grid edit, the specific sign types (products) that the task is related to, since you could be working on more than one, and there's thousands of products, so I'm trying to limit the selection to ONLY the sign types related to that specific project. I'd think this works but it doesn't​. It's like a chicken-and-egg or something isn't working right. I can't select any STs (products) because PT Chains (join table) seems to not be inheriting the associated lookup field from the task. Any clues? Thanks! ------------------------------ Andrew Ryder ------------------------------13Views0likes2CommentsPossible to add an 'Other' Option to a conditional dropdown?
I know this isn't a native capability, but sometimes we can trick QuickBase into certain things. I was trying to come up with a slick way to use formula fields so that I can add an 'other' option to my conditional dropdown. For example, if I had US States as my first selection, then cities as my second, could 'Other' be listed with the cities? ------------------------------ Mike Tamoush ------------------------------12Views0likes4CommentsConditional Record Pickers in Grid Edit
Hi everyone! Trying to come up with a workaround for the 1000 record limit imposed upon record picker selections and thought maybe I can narrow this down by setting up some conditional record pickers. We currently have 2000+ records to filter through but I wanted to set a preliminary record picker to filter the results by state. This appears to work on the form but when carried over to grid edit we first get an error message that reads 'First choose State/Region' (even after it's already selected). Even if we select State/Region then save, the second record picker still pops up in a separate window with 'No records found' to select from. Anyone have any ideas on what might be wrong and how we can make this work? ------------------------------ Marissa Zepeda ------------------------------11Views0likes2CommentsWhat causes Conditional Dropdowns not to work in editable report links?
I've used conditional dropdowns in editable report links before, but am having trouble now. I have a formula field that is what my condition relies on. If I add a child in the typical way, the formula field is populated (it's just the record ID of the grandparent), and the conditional dropdown works as expected. If I have the child table in an editable report link, and then try to use the conditional dropdown, the lookup field (used for the condition - the grandparent record id), is not populated, and therefore I can not select from my dropdown. What could cause this? Update: Found this in the community. This is my problem. "if the conditional drop-down is dependent on a value from the parent (most likely scenario), it cannot be used in an 'editable' report to add new child records. Reason being is the child record doesn't exist thus it doesn't have the lookup value that is controlling the conditional behavior. " ------------------------------ Mike Tamoush ------------------------------9Views0likes0CommentsCascading Drop-down - Multi-select field
Good Afternoon Can i create a cascading drop-down for the following set-up and if so, how: Parent: State Child (Multi-Select): Medicaid Contracts Thanks, Lashell ------------------------------ Lashell Thomas ------------------------------9Views0likes3CommentsCategories & SubCategories
If I have a Multiple Choice field "Categories", and another multiple choice field "SubCategories"... can what's selected in the Categories determine what options there are in the SubCategories? ------------------------------ Megan Hardison ------------------------------9Views0likes2Comments