Trying to build connected records
Table 1 - Requirements Table 2 - Meetings For each requirement there can be multiple meetings, owned by separate sales rep. I already have these two tables, Now if SalesPerson_A has a Meeting_1 for Requirement_1 then an associated record is created in Table 2 - Meetings, but if the same SalesPerson_A has 5-7 follow up meetings for the same Requirement_1 then 5-7 more separate associates records are created and we have created a field dropdown - Round of meeting where we are manually managing, 1st, 2nd, 3rd, etc to keep track, then we are manually copy pasting the previous meetings links in the coming up meeting to access them. this is too outdated and time taking. Also SalesPerson_B can also have a Meeting_1 for Requirement_1 then another new record is created in Table 2 - Meetings n for further follow ups its same manual way. What i want to achieve is that if SalesPerson_A has a Meeting_1 for Requirement_1 then an associated record is created in Table 2, Called Record 1, then I can have someway to keep all the next rounds of meeting under the same, each meeting is different, we have different agenda, people we are meeting, meeting links to join so for each record here there is a lot of information we need to enter, also various fields about how that meeting went, etc. need to manage this separately for each round. what can be the best way to achieve it. we never know we will 1 only or 7 or 10 meetings for a requirement.2Views0likes0CommentsParent to Child Reference Field
When making relationships between parent and children records I understand how to add additional lookups. But when you do that then those fields need to be "updated" when adding a new child. What I am seeking is a way that when a child record is created, and related to a specific parent, that the child record would show the value of additional fields from the parent. Example: Parent record has Name, Address, Phone Number, Favorite Color Child record has Child name, lookup field to select parent which would bring down the Parent Name and Favorite Color Currently when setting the relationship I would connect on Related Parent then add the lookups for Parent Name and Favorite Color, but when actually creating the new Child record once I select the related parent, the Parent Name and Favorite Color are not populating. If I want those to display the value, I have to manually update those fields (thus not benefiting from setting the relationship to the Parent). What am I missing? This seems like an easy ask but for the life of me I'm just not seeing a pathway to make this work.Solved15Views0likes2CommentsPrimary and Secondary Contacts from Table
I'm pretty sure this is a simple many-to-many relationship, but my brain hitting a wall and cannot comprehend how to set this up. We have an app in development where employees can submit reports of things happening in their day to day. Each report is then "assigned" to a person or department from a Responder table to follow up. I most cases, each report will only have one Responder so I have a normal one to many relationship set up currently. Now, occasionally, we have a situation where there will be a Primary Responder, but another department/s or person/people are included for line of sight/further conversation, ie Secondary Responder/s. I would like to have two fields, one for primary and one for secondary so I can differentiate between the two when the Pipeline kicks out the email to everyone. Is this a simple many-to-many relationship or is this going to be a bit more complex? Thank you!Solved21Views0likes2CommentsHelp 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 relationships35Views0likes2CommentsCant See Associated Records
Hi i table 1 app - 3 tables, table 1, table 2, table 3 now i have relation of one to many from table 1 to table 3. this relationship is old and has been working fine but suddenly i cant see the associated records from table 3 at the end of the record in table 1. they use to populate properly earlier. i have not changed anything in the relationship, cant understand why getting this error, it says " sorry...error retreiving data Attached the image as well. Only thing i can think of is another admin, was asked to delete all the unwanted reports so he may have deleted the associated report from table 3. if yes, how can i recreate the same. ? or any other reason for this problem.Solved22Views0likes5CommentsUser 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.24Views2likes1CommentApp-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:22Views0likes1CommentCan I create a single field that displays record owners from a child table
Hi, The use case for my application is for users to track their testing results - there is a parent table for requests and a child table for activities (i.e., test results). I am wanting to create a field within the Parent table that lists all of the people who have submitted an activity for the parent request. Any ideas?Solved35Views0likes3CommentsCalculation/Performance Limits Inquiry
Hi all, I'll try to keep this as brief as possible. I'd like to know if anyone has a similar sized application in production and if they see any performance issues as it pertains to record loading and report loading. I have an Accounts table (table A) that will have 1,500 records total at any given time. This table has 3 children tables B, C, and D with 72,000; 168,000; and 168,000 total records at any given time, respectively. These children records will all have an Account# to tie it to their parent. On table A, I need to keep up to 4 years worth of data (Current Year, Prior Year, etc.). As a result, I will need about 1,500 to 1,750 currency summary fields per year (6,000 to 7,500 in total). This number then gets doubled because Quickbase does not have a built-in way to display numbers in Accounting format, so I need an additional 6,000 to 7,500 rich text formula fields. At no point in table A should I ever need a report with more than 12 columns of calculated summary fields for all 1,500 Account records. This is the max performance need. On the forms, I plan to "only" have 6,000 to 7,500 of the 12,000 to 15,000 total fields displayed. This will be broken across 4 different tabs (hoping that improves performance) for each year of data. Then each tab will be broken into 6 sections, which can be pre-minimized if it will help load times & performance (Actuals, Budget, Forecast, Actuals VS Budget, Actuals, VS Forecast, Budget VS Forecast). This table A is my biggest concern. If you care for additional context: In addition to this, table A will be a child to table E (Summary Report Rows). There will be 12/13 total Summary Reports (table F; parent to table E), made up of about 168 table E records. To restate, the 168 records will be parents via 3 relationships to the Accounts (table A). There is 1 relationship per key/vital column in the Accounts table. These will be running calculations based on the summary field calculations in table A. I'll leave it at this for the time being to see if anyone is able to take the time to respond. At the end of the day, I've never built something with this many calculations and I'm not entirely sure on the order of operations for Quickbase when it comes to forms. Regards, CurtisSolved79Views0likes10CommentsVLOOK-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 !18Views0likes1Comment