# Record in relationship not adhering to relationship rules

**URL:** <https://the.fmsoup.org/t/record-in-relationship-not-adhering-to-relationship-rules/4762>\
**Category:** Questions\
**Tags:** relationships\
**Created:** [March 25, 2025, 1:23pm UTC](https://the.fmsoup.org/t/record-in-relationship-not-adhering-to-relationship-rules/4762 "2025-03-25T13:23:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![DeanAyalon](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@DeanAyalon](https://the.fmsoup.org/u/DeanAyalon)\
**Post date:** [March 25, 2025, 1:23pm UTC](https://the.fmsoup.org/t/record-in-relationship-not-adhering-to-relationship-rules/4762/1 "2025-03-25T13:23:18Z")

</div>

Hi there, I'm having a weird relationship problem  
I've got a relationship set up between the table `ASSIGNMENT` and `Assignment » Exams` like so:

Schedule ID = Schedule ID  
Quote ID = Quote ID  
\_One = Header  
\_One = Tested  
Segment = Package Segment

It worked flawlessly for years now, only the tested Exam headers related to that assignment's schedule and quote segment were listed

However today I found an Invoice with a row that should not have been there  
It seems the relationship did not filter one of the rows

The thing is, checking the data, everything seems ok  
`_One` is a calculation field that of course has not changed its value from 1 (evaluated as Number)

All the Exam's data matches, except for the tested boolean (also Number)  
The Exam is listed within the relationship regardless of me setting the `Tested` field to 0 or empty!

Any idea what could be the cause?

 ![Listed record not matching relationship](https://canada1.discourse-cdn.com/flex030/uploads/fmsoup/original/2X/e/e04963403b6e989dc73eb7fca32e862dec90f491.jpeg)

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [March 25, 2025, 7:40pm UTC](https://the.fmsoup.org/t/record-in-relationship-not-adhering-to-relationship-rules/4762/2 "2025-03-25T19:40:37Z")

</div>

That could be cached data getting in the way. You could force a refresh of the data on the client side. Sometimes wacky indexes are fixed by quitting FileMaker and restarting.

---

<div class="post-metadata">

**Author:** ![DeanAyalon](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@DeanAyalon](https://the.fmsoup.org/u/DeanAyalon)\
**Post date:** [March 25, 2025, 8:01pm UTC](https://the.fmsoup.org/t/record-in-relationship-not-adhering-to-relationship-rules/4762/3 "2025-03-25T20:01:49Z")

</div>

It has been reported by one user, and observed by me, so it's not client-sided  
Restarting the server itself has also not helped

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [March 25, 2025, 10:20pm UTC](https://the.fmsoup.org/t/record-in-relationship-not-adhering-to-relationship-rules/4762/4 "2025-03-25T22:20:00Z")

</div>

If a backup copy running locally also shows the problem then you need to rebuild the index for that field. If it doesn’t show the problem then it is an issue with cached data.

---

<div class="post-metadata">

**Author:** ![DeanAyalon](https://avatars.discourse-cdn.com/v4/letter/d/aeb1de/32.png) [@DeanAyalon](https://the.fmsoup.org/u/DeanAyalon)\
**Post date:** [March 25, 2025, 11:11pm UTC](https://the.fmsoup.org/t/record-in-relationship-not-adhering-to-relationship-rules/4762/5 "2025-03-25T23:11:12Z")

</div>

That was it, bad index!  
I wonder what causes this

Thank you 🙂

---

<div class="post-metadata">

**Author:** ![Malcolm](https://yyz2.discourse-cdn.com/flex030/user_avatar/the.fmsoup.org/malcolm/32/196_2.png) [@Malcolm](https://the.fmsoup.org/u/Malcolm)\
**Post date:** [March 25, 2025, 11:22pm UTC](https://the.fmsoup.org/t/record-in-relationship-not-adhering-to-relationship-rules/4762/6 "2025-03-25T23:22:39Z")

</div>

> [@DeanAyalon](#):
>
> I wonder what causes this

I blame photons.
