Child Table Field Question
I have a table called "Crane Inspections" that is the child table of a table called "Open Crane Deficiencies". I am trying to have a way to put in deficiencies (up to 4 in one form) that are either existing (noted on previous inspections and still an issue) or new. On the crane inspection form, a crane is selected from a multiple choice field, 23 different questions are completed, then deficiencies (existing or new) are annotated at the bottom. I have a way that this works now, but I am trying to make better. Right now, I have a pipeline that triggers when a new crane deficiency is put in the form (also up to 4 new ones) and creates open deficiency records in that parent Open Crane Deficiencies table. Our maintenance department goes and works on correcting the deficiency, then closes it out which deletes the record from that table. Meanwhile, on the crane inspection form, that previous open deficiency option will no longer be one on the existing crane deficiencies multiple choice field (the table-to-table relationship field). My more ideal end state is rather than have to manually select up to 4 existing deficiencies every time an inspection is completed, I would like for the up to 4 fields to be automatically populated with the existing deficiencies from the parent table. Then some way for the inspector to confirm those are still deficiencies, or enter new ones in as I have before. Please let me know if there is any clarification needed. Any help would be greatly appreciated!
Can you summarize a status for a record that has multiple child records?
I have a parent table (Requests) and a child table (Activity Log) - each Request can have multiple Activities. I am trying to get a summary of the Status logged in each activity to get an understanding of the current status of the Overall Request.SWEET CONNECTIONS: The Scoop on Relationships
What Is Sweet Connections? Sweet Connections takes you on a learning journey with Miss Cone, the owner of a frozen dessert store. Through her story, you’ll learn foundational concepts like creating relationships, importing data, building formulas, and more. Each module is packed with practical tips that will help you apply these skills to your own apps. How Does Sweet Connections Work? The course is divided into four engaging modules: Cuppa Foundations: Learn the basics of app setup, including creating tables and understanding relationships. Scoop Techniques: Master advanced features like formulas, snapshots, and data imports. Topping Triumph: Explore summary fields, conditional dropdowns, and reporting tools to gain deeper insights. Cherry on Top: Bonus tips and tricks, including best practices for naming fields and maintaining data accuracy. Why Take This Course? Building relationships between tables is essential for creating efficient apps that work seamlessly with your data. By completing this course, you’ll gain skills that will save time and make managing your organization easier. Start Building Relationships Today! We offer this course in three formats. Choose your preferred learning style: On-Demand Training: Access this course anytime at Quickbase University. Semi-Private Training: Join other customers in an interactive session where you build alongside an instructor. Private Training: Contact your Account Executive or CSM to schedule a session exclusively with your organization.
Limit Relationship Choices based on another field..
So I have a table, Purchase Orders. That table is a one to many child of Jobs. It's also a one to many relationship of Daily Reports. Daily Reports is also a child of Jobs. What I want is for user A to login, and enter 5 POs, and link them to Jobs. Then, user B logs in and clicks the "Related Daily Report" field and it's limited to ONLY the jobs selected by user A. Is this possible?
Relating Multiple Records from another table
I am trying to create a new process for tracking manual revisions in our training curricula that we've built into our project manager app. Each change may affect multiple curricula, and multiple lessons within it. I would like to be able to add a change, select the curricula it applies to from a dropdown, and then have another dropdown of lessons from the curricula. I have the relationships set up the way I want it now, but I can only select one curricula and one lesson to relate to each change record. I've seen the many to many option of having a table in the middle, but I'm struggling to figure out how to apply that to my scenario. I remember an Empower session that related multiple work equipment to one work order using a multi select and a Pipeline to relate that to an Equipment table but I can't remember how it was done in the end. I'd love any ideas!
Inventory Tracking
I have these tables: Trailer Trailer Inventory Item Item Usage Currently my structure is set up like this: Each Trailer has many Trailer Inventory records Each Trailer Inventory has many Item Usage records Each item has many Item Usage records Each Item has many Trailer Inventory records This is what I am trying to do: Enter in an item usage record and subtract from Trailer Inventory. When the item usage record is entered, I know the Trailer ID & The Item ID. I need these two IDs to match to a record in the Trailer Inventory table and subtract the quantity used from the Starting Quantity in that line. Example: In Trailer Inventory, I know that my starting quantity for Item #1 on Trailer #1 is 10. I then go enter in an item usage record and I enter that I am using Item #1 on Trailer #1, and I'm using 5 of them. I want that to go match up to the Trailer Inventory record using those two IDs, and subtract the 5 used from the original 10 that we started with. I have a summary field on the relationship between Trailer Inventory & Item Usage that summarizes the "quantity used" from the item usage table. I was trying to add criteria to this summary field to say only summarize the records where the Trailer ID & the Item ID match on both tables, but I can't seem to get it to pull in the correct fields in the drop downs so I don't think my connections are set up properly. Can anyone help with this?
Way to do Editable Lookup Fields?
I was wondering if there is a way to do an "editable lookup field"? I have 52 tables - one strictly for contact information for all US states, and one for each state that has some of that contact information, as well as some added columns for tracking our data on them. These tables do need to be separate with the way our workflow and filters need to be set up. I would like to be able to set it up to where if we are working on the tracking table and we find a better email, if we update it on that document, it updates on the master contacts. And vice versa, contacts updates our state's tracking sheet. I believe lookup fields are non-editable by nature, so I didn't know if you all would recommend something? I have lightly tested out a pipeline method for this, but I would need many pipelines to accomplish this effectively.Add Existing Child Records from New Parent Record
I have an app where people can have many related child documents. Now, the app requirements have expanded, so that documents can belong to many people. I want users to be able to select multiple existing people records when they create a new document record and uploading the file attachment, basically like a multi-select text field but for existing soon-to-be child records. I'd prefer to avoid creating a many:many assignments table for the sake of simplicity but if I have to then I have to. Any ideas?
