1 Reply Latest reply on Aug 31, 2014 10:03 PM by philmodjunk

    Database does not create related records when specified in a relationship



      Database does not create related records when specified in a relationship


      FileMaker Pro



      Operating system version

      MacOS 10.9

      Description of the issue

      This should not be complicated; two tables, Bulk Lots and Specimens, are related by an indexed text field, PCGSNo.  The definition of the relationship specifies creation a new record in the related table through this relationship.  This does not happen.  It is not clear at all to me why this does not work, as I have been able to do this in other contexts, and wonder if other users have encountered inconsistent results with this feature of the program.

      Steps to reproduce the problem

      The relationship is created; a new record is created in one table.

      Expected result

      A new record should appear in the related table containing the matching value in the related field.

      Actual result

      No new record appears in the related table.

      Exact text of any error message(s) that appear



        • 1. Re: Database does not create related records when specified in a relationship

          Take a look at what that check box selected option actually says. "Allow creation of records via this relationship". In other words, selecting this option makes it possible to create records from the context of the related record. It does not make it an automatic process.

          The typical use of this option is for when you have a one to many relationship and you enable the "allow..." option for the table occurrence on the "many" side of the relationship. If you then put a portal to the "many" table on a layout based on the "one" table occurrence, an extra, blank, "add row" will appear in the portal below the last portal record shown in the portal. If you enter data into a field in this "add row" FileMaker will create a new record in the portal's table and copy over the value of the match field of the layout's current record, thus linking the new portal record to the current layout record.

          In most cases, there is no need to automatically create a related record in one table simply because you created a new record in the other table. That's because you can quite easily create as many related records as you need on an "as needed" basis.