# Caveat on Creation via relationship (no records in first table)

**URL:** <https://the.fmsoup.org/t/caveat-on-creation-via-relationship-no-records-in-first-table/3717>\
**Category:** Heads-Up!\
**Tags:** scripting, relationships, filemaker\
**Created:** [September 27, 2023, 2:51pm UTC](https://the.fmsoup.org/t/caveat-on-creation-via-relationship-no-records-in-first-table/3717 "2023-09-27T14:51:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![iwitschi](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/iwitschi/32/709_2.png) [@iwitschi](https://the.fmsoup.org/u/iwitschi)\
**Post date:** [September 27, 2023, 2:51pm UTC](https://the.fmsoup.org/t/caveat-on-creation-via-relationship-no-records-in-first-table/3717/1 "2023-09-27T14:51:18Z")

</div>

Hi, I just came across a caveat while using the feature "allow creation of records in this table via this relationship" in the relationship-graph.

If you build up your relation with a global field in table A in order to create records in table B, **make sure table A contains at least one record**. Even if you are never going to use this record. Otherwise FileMaker will return the error "record missing" and just not create a new record in table B.

(use case for an empty table: when using a separate table exclusively for global fields)

---

<div class="post-metadata">

**Author:** ![FabriceN](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/fabricen/32/2506_2.png) [@FabriceN](https://the.fmsoup.org/u/FabriceN)\
**Post date:** [September 28, 2023, 7:41am UTC](https://the.fmsoup.org/t/caveat-on-creation-via-relationship-no-records-in-first-table/3717/2 "2023-09-28T07:41:57Z")

</div>

Yes, it's an old issue.  
That's why you should pay attention to having a record, even in a table with only globals.
