Forum Discussion
IvanWeiss
6 years agoQrew Captain
Unfortunately, that looks to to me like the exact issue. You cannot pass through the join table....
The only thing you could do is look everything down to the join table and use that for your reports. But you cannot move the data up and down to my knowledge.
I really think you need to relook at that table design.....
------------------------------
Ivan Weiss
------------------------------
The only thing you could do is look everything down to the join table and use that for your reports. But you cannot move the data up and down to my knowledge.
I really think you need to relook at that table design.....
------------------------------
Ivan Weiss
------------------------------
PaulPeterson
6 years agoQrew Member
Can I use a webhook or automation to update the other tables?
------------------------------
Paul
------------------------------
------------------------------
Paul
------------------------------
- MarkShnier__You6 years ago
Qrew Legend
I will see if I can find time later this weekend to get my head into this thread.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------ - IvanWeiss6 years agoQrew CaptainI am going to have to defer you to Mark here as I dont know much about webhooks and while I guess you could do something with automations sounds complicated to me. But he is way more skilled than I am. Sorry I couldnt help!
------------------------------
Ivan Weiss
------------------------------ - PaulPeterson16 years agoQrew Assistant CaptainThe thought I had late last night was to eliminate the relationships and bridge table and use a webhook to update the installation table when the verification table is updated.
------------------------------
Paul Peterson
------------------------------ - MarkShnier__You6 years ago
Qrew Legend
I think that you are way overcomplicating this.
From your problem description there are installations and they need to be audited or verified.
I see two obvious choices.
The first is simply to have the verification fields directly added to the installations record. Separate them into their own section or Tab and use the Roles to control which Roles can see and edit those audit fields. You can have form rules for example.
If there is a valid reason that I'm not currently understanding to have a separate tables to hold the records for Verifications, then clearly the Verification should be a child of the Installation as the Installation record is created first.
If there is some need to get the some of the data from the child Verification record up to the parent Installation record such as a pass/fail or a score, then there are several easy techniques to do that which I can explain.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------ - PaulPeterson6 years agoQrew MemberAs Ivan pointed out earlier, the app is in need of some significant refactoring. The installation table is already in serious need of normalization and I would like to avoid adding more design issues.
There are currently 13 services in the verification table. I need to send back the results from 2 checkboxes and 4 text fields for the services the customer is using along with the last modified by user and last modified on timestamp. I would greatly appreciate your suggestions for sending this data back to the parent table.
------------------------------
Paul
------------------------------ - MarkShnier__You6 years ago
Qrew Legend
This will not need Automations or webhooks. Does each Site info only have 1 Verification record?
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------ - MarkShnier__You6 years ago
Qrew Legend
I will assume that it is just the only or the most recent Audit info that you need to float up to the Parent record.
Kill the Bridge table. You do not need it.
Make a relationship directly where 1 Site info has many Audits.
Make a summary maximum of the Record ID# of the Audit, call it [Record ID# of Most Recent Audit].
Make a new reverse relationship where 1 Audit has many Site Info but for the reference field on the right side use that field [Record ID# of Most Recent Audit].
Then simply look up any field you want from Audits to Site Info.
If you for some reason you do want to retain the bridge table (not needed though, I re-state) , then you would need to look up the audit data down to the bridge table.
Then you would need to do that same reverse relationship between the Site info and the bridge table.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------ - PaulPeterson16 years agoQrew Assistant CaptainThank you Mark,
Yes, each project should only have a verification at the completion of the project.
It's looking like a busy day today, but I will look into your approach this evening after the official work-day is complete.
------------------------------
Paul Peterson
------------------------------