How to relate two tables with the key to a third table?
In Referral (key Record ID), there is a field called Referring Contact - which is a key for the table Contact. In Activity (key Record ID), there is a field called Activity Contact - which is a key for the table Contact as well. It also has a field called Team Member ID - which is a key for the table Team Member. The users want to know, for every Referring Contact in table Referral, the name of the Team Member who had an activity most recently with that Referring Contact. The Activity table contains this information but I cannot figure out how to get it into the Referral table to report - I think the two tables should be related, then there should be a formula field that brings the (newest) Activity record, with its associated Team Member, into the Activity Record. But how to relate the two tables, since the "matching" Contact fields are not the key of either table?
Way to do Editable Lookup Fields?
I was wondering if there is a way to do an "editable lookup field"? I have 52 tables - one strictly for contact information for all US states, and one for each state that has some of that contact information, as well as some added columns for tracking our data on them. These tables do need to be separate with the way our workflow and filters need to be set up. I would like to be able to set it up to where if we are working on the tracking table and we find a better email, if we update it on that document, it updates on the master contacts. And vice versa, contacts updates our state's tracking sheet. I believe lookup fields are non-editable by nature, so I didn't know if you all would recommend something? I have lightly tested out a pipeline method for this, but I would need many pipelines to accomplish this effectively.
Add Existing Child Records from New Parent Record
I have an app where people can have many related child documents. Now, the app requirements have expanded, so that documents can belong to many people. I want users to be able to select multiple existing people records when they create a new document record and uploading the file attachment, basically like a multi-select text field but for existing soon-to-be child records. I'd prefer to avoid creating a many:many assignments table for the sake of simplicity but if I have to then I have to. Any ideas?How to display related field value from a grid edit dropdown selector (rather than record id#)
I have a grid edit table report that requires the user to select the "Related Content Allocation" before editing the rest of the columns/fields. However, the dropdown is displaying the related field's record ID, which isn't very user-friendly. Is there a way to display other related field values in this dropdown rather than the record ID# easily? ------------------------------ Matt Makris ------------------------------
Question on Connected Tables
Our company has several apps, it has become apparent to me that we have a lot of common information in tables across these apps. It has also become apparent that we could leverage connected tables to help manage this, so that we only need to update a table in one app as opposed to updating the same information in several apps. I'm wondering though how one would handle the existing table relationships. Example. We have an app (App A) that has a 'Customer' table. This table could be used in another app (App B) which has it's own 'customer' table. But the second app's table has several existing child tables. Would I be able to just make a new connected table from App A to App B, and then just sever the existing relationship with one of App B's child tables (but keep the reference field), then make a new relationship with the connected table? That seems possible to me, but I'm wondering about the key field in the connected table. I wouldn't be able to use the key field the source table is using because in App B the 'Customer' table uses a calculated key. Would I be able to define a new key field in the connected table so that the child table keys could be mapped to it?Many parent records on a single child record
Hi everyone, I'm having some issues building the following: I need to build a table where a laboratory analyst can record analytical standards that they have prepared. I have one table that records reagent inventory and relevant reagent information like lot number, date received, expiration date, manufacturer, etc. For analytical standards that use only one reagent, this is simple to build with a one-to-many relationship. However, some standards are made with multiple different reagents. How do I get multiple parent records on a single child record? Any help would be appreciated!
Intuitive way to pick line items from a list
I want to allow my clients to create a Purchase order and then pick items from inventory to be line items of Purchase Order. The normal way to do this would be to display a report of available inventory on the Purchase Order record and then let the user pick which of the items he would like to be part of the purchase order. Is there an intuitive way to do this in Quick Base?How to Show Conditional Data in a Related Join Table
Hello all, I have an app with three tables: Faculty Records - Contains the various credentialing programs available for physicians. Physician Info - Stores static information like name, title, and person number. Physician Credentials - A join table that shows the relationship between physicians, credentials, and the dates those credentials were approved. The relationships between these tables are as follows: Here’s the issue I’m facing: One specific credentialing program from the Faculty Records table includes advanced privileges (checkboxes) unique to individual physicians. These privileges: Are only relevant to this one credentialing program. Differ from person to person. Ideally, should appear in the Physician Credentials table alongside the credentialing program, approval dates, and physician name. While I could add the advanced privileges to the Physician Info table, how could I then see them in the Physician Credentials table? Would queries be a solution for this? (I’ve never used those before.) What’s the best way to structure this? Thanks in advance for your help! Meag
