Relationships - Parent, child and proxies
Def a noob question, but I've tried everything! I have Registration Table:
UUID [key], alphanumeric code means nothing
Name
Telephone number
Transfers table: We get a list each month...
Forum Discussion
In order to get them to match up automatically, you would need to set the Phone # field in your Registrations table as the Key field. You should try this first in a Copy of the app if you have never changed a Key field.
I don't know how many relationships the Registrations table has now where it is the Parent, but if it has many relationships, then you definitely need to test or look to a QSP for some assistance,
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
I don't know how many relationships the Registrations table has now where it is the Parent, but if it has many relationships, then you definitely need to test or look to a QSP for some assistance,
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
Thanks appreciate it!
I can't use the phone number as a primary key as it may change for some people.
On the QSP front, I've contacted the makers of DC many to many, Veilsun and Juiced technology's triggers. Are there any others I should consider?
Cheers
Rory
------------------------------
Rory Crew
------------------------------
I can't use the phone number as a primary key as it may change for some people.
On the QSP front, I've contacted the makers of DC many to many, Veilsun and Juiced technology's triggers. Are there any others I should consider?
Cheers
Rory
------------------------------
Rory Crew
------------------------------
- Rory,
I highly recommend Juiced Triggers. This has a great Search Feature will allow you to add the record to the Transfers Table and then the Trigger will find the correct Parent in the Registration table and relate them.
------------------------------
Don Larson
Paasporter
Westlake OH
------------------------------ - Rory,
Making Registration a parent of Transfers would create the architecture required for the summary field.
It sounds like you're looking for is something like:
- Transfer Added
- Find a Registration that matches the Transfer's [Telephone Number]
- Write the Registration's [Record ID #] to Transactions [Related Registration]
I'm not aware of a native QuickBase function that will accomplish Step 2 (search then add.) However, you might be able to get users to make that connection for you without even knowing it:
- Create relationship of Registration to Transfers (one to many)
- Make [Telephone Number] the proxy field for [Related Registration]
- Make [Related Registration] required
- On the Transfer table, make this new [Telephone Number] the way users select [Telephone Number] for a Transfer
- When a record is saved and [Related Registration] changes, copy new [Telephone Number] to old [Telephone Number] field
- This can be accomplished via Form Rule, Webhook, or Automation
- In your UI, always display old [Telephone Number] and only allow users to edit new [Telephone Number]
By using this method, the actual [Telephone Number] receiving the Transaction is preserved (valuable for audit purposes). The Registration also stays tied to this Transaction even if Registration record's [Telephone Number] changes. As a bonus, this will make sure your users are always making Transfers to valid Registrations. After all, they're already entering [Telephone Number]. They might as well use the method that ties everything together! You'll also save your users some clicks (1 click and 10 keyboard presses goes to 2 clicks)!
------------------------------
Evan Westbrook
PRIME Developer
Harder Mechanical Contractors Inc.
Portland OR
------------------------------
