You create a extra table where you just store keys from the two tables that you like to work with
Company - CompanyContact - Contact
(Company ID) - (Company ID and Contact ID) - (Contact ID)
As I mentioned, I have already done that. The question is concerning they layout.
1 of 1 people found this helpful
I would prefer NOT to use a layout for the "join entity table" BatchesToTreat, but enter it all in the Treatment
Assuming you have a portal into the join table on your Treatment (T) layout that is based on a relationship that allows record creation (i.e. in Treatment --< Join, the join TO has this option checked), you can put the Batch (B) ID field into the portal and use a value list to select a batch (ID).
So in your join table that has foreign keys TID and BID, the TID is auto-filled via the relationship definition, and BID is entered by you – instant join record.
A more flexible approach is to use a Cartesian relationship ( x ) between T and B, where
T::anyField x B::anyField
Put a picker portal into that relationship on your T layout (stash it away in a popover), and use scripting to select/deselect B records, then add the selected B records as new join records.
Here is a sample file to demonstrate the picker portal concept.
Simply replace “Estimate” with “Treatment”, and “Product” with “Batch” (a database is a database is … )
Note that in a portal you are not limited to a few fields or constrained by index considerations – just display whatever fields you need to identify an entry. Also, you can constrain the display more easily, and add selections in batch mode.
EstimatesEasy_eos.fmp12.zip 78.1 K
That sounds great! But how do I get hold of the sample file?
Open the post (proper – not just display it in the Activity Stream) and download the attachment.