Forum Discussion

DianeSinawi's avatar
DianeSinawi
Qrew Trainee
24 days ago

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?

4 Replies

  • 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.  

    • DianeSinawi's avatar
      DianeSinawi
      Qrew Trainee

      Employee ID is not the key field in Targeted User parent table, its Record ID. Since that table is also a parent table in other relationships, if I change the key field to be Employee ID in this relationship, will it automatically change for other relationships, or are they all independent? I don't want to mess up other relationships

      • MarkShnier__You's avatar
        MarkShnier__You
        Icon for Qrew Legend rankQrew Legend

        You can change the key field of a table and it will re-link all of the children on the child tables based on that employee ID field. But a less drastic thing to try next would be to simply mark the employee ID field as unique on the Parent record and that may be enough.  Is i5 currently marked as Unique in field properties.