Skip to main content
Question

problem populating relationship field from import

  • Jul 25, 2025 5:48 PM UTC
  • 3 replies
  • 247 views

Forum|alt.badge.img+4

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?

3 replies

Forum|alt.badge.img+6
  • Qrew Member
  • Jul 25, 2025 9:04 PM UTC

.


MarkShnierYou
Forum|alt.badge.img+24

Can you show a screenshot of the relationship where one targeted user has many fishing attempts. What is the key field of the targeted users table. It should be the employee ID field.  


Top Step
Forum|alt.badge.img+12
  • Observing
  • Oct 26, 2026 6:20 PM UTC

Yes, that's why. Employee ID on Phishing Attempts is a lookup from Targeted Users, and a lookup only fills in when the record is linked to a parent.

The easiest fix is to mark Employee ID as unique on the Targeted Users table. Open that field's settings on Targeted Users and check Unique. Your existing Employee IDs have to be unique already for it to save.

Once it's unique, the Employee ID lookup shows up as an import target on Phishing Attempts. Map your spreadsheet column to it and Quickbase links each new record to the matching Targeted User, so the rest of the lookups fill in too. Your role needs Modify access to that field.

If you'd rather not change the field, export your Targeted Users with Record ID# and Employee ID. In your phishing spreadsheet, do a VLOOKUP on Employee ID to pull in each person's Record ID#.

Then import that column straight into the reference field on Phishing Attempts, usually called Related Employee or Related Targeted User. That links each record to the right person and all the lookups fill in.