problem populating relationship field from import
In a new QB app we created, we have a table "Phishing Attempts" where we want to create records by importing a spreadsheet. We also have a table "Targeted Users" which has employee info such as Employee ID, email, position, etc. Phishing Attempts table has a relationship with Targeted Users table, where we have the Employee ID field from Targeted Users included in the Phishing Attempts record form along with lookup fields that are automatically pulled from Targeted Users table. The spreadsheet we want to import to create new records in Phishing Attempts table includes an employee ID number. When we import the spreadsheet, we select the target field Employee ID in the Phishing Attempts form. The problem is that the Employee ID field in the Phishing Attempts form is not populating when we do the import. The ID number in the spreadsheet matches exactly what is in Employee ID in Targeted Users table. Is this not working because the Employee ID field in Phishing Attempts is pulling from Targeted Users table? Is there a way to get this to work?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.
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 relationshipsUser 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:
