Help connecting Table to Table Relationships
Hi, I have 4 tables Site table - houses all site info including site ID# which is the unique identifier to be used to relate/connect all tables. Risk table - houses all the risks. 1 site can have many risks Milestone table - Each risk can have many milestones Site Risk Register - Joining table that has all the risks and milestones relating to each site on one table I'm struggling to figure out how to connect these tables. I figured all tables need to have that site id# field in order to connect. So I created a one to many relationship with the Site table and the other 3 tables so all 3 tables have a site id# lookup field. Then I created more relationships. One Site Risk Register has many Risks, One Site Risk register has many Milestones and then I also made One risk table has many milestones. I added dummy data in the tables but it is not reflecting in the Risk Register join table. Can I get help on what I did wrong and how to properly set up these table relationships
User Focus Technique Demo on April 15th
Just a heads up that I will be doing a demo of the User Focus Technique on Tuesday April 15th. Register to attend or at least to get access to the recording after the session. https://community.quickbase.com/discussions/app-builder-discussion/aprils-app-builder-agenda-for-april-15th-2025/90452 Register Here Agenda for the App Builders Qrew Meet Up Tuesday April 15th at 12pm EST: Mark Shnier, owner and developer of Your Quickbase Coach, who will present some use cases solved with the User Focus Technique, including calculating distances between addresses and quickly assigning team members to a project. This Technique should be in your toolkit as it's really useful and provides a great End User experience. This session will include an app by Mark that is now available in the Exchange that you can download and apply what you learned from this session right away.
App-to-App Permissions/Relationships
Hello! I am building my second app and trying to tie it into my first -- it feels like it wants to be separate because the users who will primarily use this app are from another department, but there is a lot of collaborative/universal information in my existing app I'd like to be able to share between the two apps, though there's too much in my initial app that the other department should not have access to, so creating a whole separate space for them and feeding in the pieces I do want shared access to feels like the best way, rather than bring them into my existing app and cull back their access. To that -- A) does that logic track properly? And B) Do they need a relationship to every table I watn them to access, including grandparent tables? I wanted them to see some grandparent info, and I notice when I run tests using them as a user, that since they're not in that other app, they only see throughput from the table-to-table access, and anything that's generating off a grandparent table just won't throughput for them, which is really surprising to me. Thanks! My view, and then that user's view side by side:
VLOOK-UP (relationschip)
I’ve made in QB a table, where we can search on a specific code and he will give the other related masterdata (out of backtable). Problem statement: The problem here is , he can only work with 1 code (80737797) - to reflect the related masterdata, so in case we have multiple codes , we are currently not able to reflect all the codes via this way. So in this case , Code 80748492 & 80830493 aren’t able to be reflected via the “Related masterdata”-fields. Is there any potential way to have this done within the same “record ID / Line” ? Is there any other opportunity to have the same outcome , but with another workaround. I know we can go for multiple record ID’s. But this I would like to avoid as it will create confusion for our partners. Many thanks !
I need help creating a snapshot field in a unique parent-child relationship.
In my app, there is a relationship between two tables, call them Table A and B. In table A, there is a column called batch date. For this field, we would like to create a new field based off of it called initial batch date in the same table. This would essentially be the first value that was inputted in the batch date field (that field has end users inputting a value often). From the research I have done, the best way to preserve original values is using a snapshot field. From what I understand all I have to do is add a lookup field to the child table, then create a new field for a snapshot that effectively references this lookup field. The problem is in this relationship, table A is the parent and table B is the child. How would I create a snapshot field for table A in this situation? So far I added the lookup field in table B, then I created the snapshot there, and then added it as a summary field in table A to reference the original snapshot. This did not seem to give the desired result. Any suggestions? Open to anything. Sorry if it is not super clear as I am only a few months experienced in QB. Thanks,
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.
