Forum Discussion

HeatherBryant2's avatar
HeatherBryant2
Qrew Assistant Captain
5 years ago

Formula to find duplicate values in one field.

Hi Community, I'm working with one table, named Jobs. In this table there are Parent Jobs and Sub-Jobs. Typically I would set up Sub-Jobs as a child table to Parent but due to the requirements of ...
Formulas and functions
Relationships
MarkShnier__You's avatar
MarkShnier__You
Icon for Qrew Legend rankQrew Legend
The challenge here is that in order to do the summary feel that you need a relationship and I suspect that the job number is not the key field to the table. What is the key field to the jobs table. Is it record ID or is it the job number

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
JordanMcAlister's avatar
JordanMcAlister
Qrew Captain
5 years ago
Could she create a same-table relationship where the job table has a relationship with itself, since each job can have many jobs?

------------------------------
Jordan McAlister
------------------------------
  • MarkShnier__You's avatar
    MarkShnier__You
    Icon for Qrew Legend rankQrew Legend
    5 years ago
    Yes, a table can be related to itself and yes one parent may have many children.  The question is what the key field is and it's it's record ID, how will the data actually get connected.  It might take some one time  Excel work.

    ------------------------------
    Mark Shnier (YQC)
    Quick Base Solution Provider
    Your Quick Base Coach
    http://QuickBaseCoach.com
    markshnier2@gmail.com
    ------------------------------
    • HeatherBryant2's avatar
      HeatherBryant2
      Qrew Assistant Captain
      5 years ago
      Hey guys,
      Thanks for the responses. Here's some more info:

      - The one-table requirement came about due to reporting and wanting to have all jobs in one table. I probably could have created two tables separately, and then a summary table for reporting. But I didn't, and at this point it's too late to turn back.
      - The key field is not the Job #, it is the Record ID#, but it could be the Job #
      - There aren't a ton of Sub-Jobs in the app yet, so ​​​If I changed the key field it wouldn't be me too messy to have to go back and relate them to the Parent Job. I have people adding Sub-Jobs from the Parent Job so I could add the Related Job # to the Add button and have QB relate the Sub-Job to the Job automatically
      - This really isn't a make-or-break the app function, it's more of a user-friendly initiative. 

      I think ​you guys solved it with the same-table relationship. Based on the info provided above do you agree?

      THANKS!

      ------------------------------
      Heather Bryant
      ------------------------------
      • DonLarson's avatar
        DonLarson
        Qrew Elite
        5 years ago
        Heather,

        Why is it too late to change the architecture?   Undoubtedly new business requirements and reporting will surface as the body of data builds.  If you can export the table, parse and import child records, it will pay you dividends in the future.


        ------------------------------
        Don Larson
        Paasporter
        Westlake OH
        ------------------------------