Use a related Deeds table to store multiple PDFs per record.
This question came up often during the last few months -> No, one PDF in one (container) field. Good news is (as erolst mentioned) that You can 'clue' as many PDF's as You like to a 'master' record if You create a separate, related table for media data
Not to sound like a newbie to FileMaker Pro (but I am, so here goes)
How DO I create a separate related table?
You don't say what your master table is, so I'll just call it Master. Each record in that table will have a masterID field. Create a separate table called Deed. That is where your container field resides. Another field in this table will be masterID, which you will enter from the master record to which each deed belongs. If you set it up right you will be able to create Deed records via a portal and have the masterID entered automatically as records are created.
As noters already, you can only insert one pdf into a container field—although it can be a multiple page document—so if you have many documents then a separate table is the way to go.
Markus Schneider wrote:
You can 'clue' as many PDF's as You like to a 'master'
“Clue” or “glue”?
You don't say what your master table is, so I'll just call it Master. Each record in that table will have a masterID field. Create a separate table called Deed. That is where your container field resides. Another field in this table will be masterID, which you will enter from the master record to which each deed belongs.
With this crucial addition: once you've set up the Master primary and Deed foreign key, you go to Manage Database > Relationships and relate Master to Deed by Master::id = Deed::id_master (or masterID).
If you set it up right you will be able to create Deed records via a portal
”Set it up right” means: check the „Allow creation of related records…” option for the Deed table while you define the relationship. That option causes a portal to display a spare portal for creating a new related record (after which you get a new spare row etc.).
While you're at it, don't forget to give the Deed table also a serial ID field (a primary key), validated as unique and non-empty; either an auto-incrementing number, or as a text field with an auto-enter option of Get(UUID). (Be aware that you need to use the same field type for a foreign key as the primary key it is intended to store.)
Create such a key field in every table (it's usually the first field I add to any new table).
Thanks for amplifying my shorthand.
The simplest method of creating a table for your existing container field is to import the container field into a new table in your file.
If you do not know how to use the import function to create a new table in the existing table, just ask.
Create an import that has at a minimum the fields
You can import other information pertaining to the container field. After the import you can delete these fields from the mother table.
You will now have the mother table and the subset child table.
In the relationship graph drag a line between the Record ID in the mother table and the same field in the child table. I would name the fields
Now you can create a portal on the Mother layout that shows the PDF records in the child file.
Thinking out of the box, here, your deeds could be combined into a single PDF file with multiple pages. Use Preview or Adobe Acrobat to do this. Then drop the single PDF file with multiple pages into your container.
This is much simpler but less easily browsed than a related table.