Passing fields from Child to Parent
Hi, I have two related tables: Request Table and a Requisition Table. The workflow is to enter the Request information first. Then from the Request table, click on the Add Requisition button to add the Requisition information. This is working as expected. When a Requisition is added from the Request form, the # of Requisition records summary field is updated correctly. What I am needing help with is passing the associated Requisition number into a field in the Requests report. Currently the # of Requisition records summary field shows on the Request report. But the Related Requisition Number or Related Requisition does not show in the report. I have to go to the Requisition Table itself, and then manually link the related Request to the Requisition. I hope this all makes sense. It is difficult to explain. Thank you in advance for your assistance.
Rollup Help
I've added a new Parent table "Cases" table to my already-established Child "Call Records" table as suggested to me earlier this week, and created a bunch of roll-up fields so that our end users can enter their fields on their call, and it will roll up to the master Cases into summary fields. Previously, we delineated calls that were subsequent calls of a same case utilizing a field on the call record ("Continuation of Earlier Case"), but it created issues of duplicate data. That said, two questions: Is there any way to create such summary but filter out answers = to "Unknown" or "Not reported", unless they are theonlyanswer? I suppose the alternative is simply to have no answer. We've used Unknown/Not Reported on multi-select text fields for the ability to require the field nonetheless, but if on a subsequent call, the data is known, I'd like to disregard "Unknowns". Can I use the roll-ups to tie to another Parent table? I'd like to tie all these to the hospitals that call us. But in theory, it could one day be more than one hospital (e.g. patient transfers, two hospitals call us). I have a summary of hospitals, which today is universally one hospital deep -- but again, within the realm of possibility to be more one day. These Case roll-up fields will power a lot of analytics that were on our Call Records previously - demographics of cases, etc., so a lot of variety in the static items creates another issue with data clarity/cleanup. Thanks!
Question about relationships
Hi there. I'm new to Quickbase and trying to learn as I go. I'm building some tables for our company and need help with the relationship between customers and their orders. I apologise if this has been asked countless times - if someone can point me to the right answer I'd be very grateful. Our company has many customers - and I've created a 'customer info' table to store their information (company name, contact info, website, phone, email, address etc). These customers can place lots of orders with us. So my second table is an 'order sheet' which has details of what they've ordered, when it's needed by, what size it is, its weight - that sort of thing. On this 'order sheet' table, I would like to have some of the customer info (company, contact name and phone number). I'd ideally like it if, when the customer name is selected from a drop-down (or similar) then their phone number, contact name and email is automatically populated. Is that possible? As a follow-up, if it is possible, and once the relationship is properly defined, can I select a customer from the 'customer info' table and then show a list of everything they've ordered? Would that require a new table? Thanks in advance if anyone can help (especially if it's explained as simply as possible!) Simon.Quickbase Actions
I am trying to make a Quickbase action... When a certain action takes place, I would like for a field to be edited, rather than having a new record created. However, the option for a field to be edited is blurred out. I need the field in another table to be edited? What am I missing?Re-establishing relationships in migrated databases
I need to understand how to re-establish relationships on existing tables that I have migrated into Quickbase. I know am absolutely missingsomething that is probably pretty obvious. Its an MSAccess database, so its SQL compliant. I have a table with important information in a field that I want to preserve. This is the field in the child table--lets call the field BigInfoValue (a numeric field) and the table ChildTable. I have a tiny table with other information in it that defines what the values in BigInfoValue mean. Lets call this BigInfoParent table, and lets call the fields BigInfoValue (a numeric field I want to relate the tables on which I've also designated the key field), BigInfoTerm, and BigInfoDefinition. I absolutely cannot figure out how to make the two tables link on BigInfoValue. When I try to create a table relationship, with BigInfoParent, Quickbase does not offer me BigInfoValue in the child table as a linking field. It creates a brand-new field called Related BigInfo something something. I've also tried to establish a table relationship with the RecordID field in BigInfoParent to BigInfoValue in the ChildTable. No dice. Quickbase just doesn't offer me the field that I think should be linked. Any help would be appreciated.
Relationships functional question
Hello! Intermediate-level user here and very much enjoyed the former QB forum - hoping to see some familiar faces on here. I am dipping my toes in the waters of fixing a Quickbase app that I didn't actually build - which is great! Something I'm thinking I want to learn more about/perhaps pursue from here. But also feels like the litmus test here - fixing my own Quickbase that I built is one thing, but now getting to know the ins-and-outs of someone else's is - wow. Anyway. One ask from the team I'm refreshing this for, I'm struggling with because I'm not sure this is possible. They want to see on the Table view, a field that populates a date from the related table of the last record. Perhaps there's a formula that I can pull to make this a field. So -- in the simplest terms, I feel like what this field needs to be is: Parent Table owns the field, and that field is points to the Record Date of the newest Child Table record. How can I do this? Is there perhaps a formula field to build? Also - I see my predecessor attempted this, and it is reporting out on several fields..... I don't quite know how to make sure my fix populates everywhere, other than editing the specific existing field. Could I just copy that field, and it'll still report on those records? I know if I "change type" of field, you can often only do that once, and it won't let you change it a second time.