Relating Multiple Records from another table
I am trying to create a new process for tracking manual revisions in our training curricula that we've built into our project manager app. Each change may affect multiple curricula, and multiple lessons within it. I would like to be able to add a change, select the curricula it applies to from a dropdown, and then have another dropdown of lessons from the curricula. I have the relationships set up the way I want it now, but I can only select one curricula and one lesson to relate to each change record. I've seen the many to many option of having a table in the middle, but I'm struggling to figure out how to apply that to my scenario. I remember an Empower session that related multiple work equipment to one work order using a multi select and a Pipeline to relate that to an Equipment table but I can't remember how it was done in the end. I'd love any ideas!
Limit Relationship Choices based on another field..
So I have a table, Purchase Orders. That table is a one to many child of Jobs. It's also a one to many relationship of Daily Reports. Daily Reports is also a child of Jobs. What I want is for user A to login, and enter 5 POs, and link them to Jobs. Then, user B logs in and clicks the "Related Daily Report" field and it's limited to ONLY the jobs selected by user A. Is this possible?
Inventory Tracking
I have these tables: Trailer Trailer Inventory Item Item Usage Currently my structure is set up like this: Each Trailer has many Trailer Inventory records Each Trailer Inventory has many Item Usage records Each item has many Item Usage records Each Item has many Trailer Inventory records This is what I am trying to do: Enter in an item usage record and subtract from Trailer Inventory. When the item usage record is entered, I know the Trailer ID & The Item ID. I need these two IDs to match to a record in the Trailer Inventory table and subtract the quantity used from the Starting Quantity in that line. Example: In Trailer Inventory, I know that my starting quantity for Item #1 on Trailer #1 is 10. I then go enter in an item usage record and I enter that I am using Item #1 on Trailer #1, and I'm using 5 of them. I want that to go match up to the Trailer Inventory record using those two IDs, and subtract the 5 used from the original 10 that we started with. I have a summary field on the relationship between Trailer Inventory & Item Usage that summarizes the "quantity used" from the item usage table. I was trying to add criteria to this summary field to say only summarize the records where the Trailer ID & the Item ID match on both tables, but I can't seem to get it to pull in the correct fields in the drop downs so I don't think my connections are set up properly. Can anyone help with this?
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?
