Table Conflicts with Integrity Rules

[pmcfarlain]

I'm trying to enforce referential integrity with some tables in my app so that I can cascade update/delete records but I keep getting this error:

 

The parent field is an autonumber and the related field is a unique integer. It's a one-to-one relationship with an inner join. Here's the relationship settings.

Any ideas?

[eunha]

You may check if there are ID records from your related table that are not present from your parent table. All referenced child records should be present on your parent table to enable the referential integrity.

[GoodBoy]

I guess it is because of the related field set as unique. They should not be unique so you can enable the referential integrity.

[GoodBoy]

It is stated under this documentation under the 'Pre-requisites'

https://howto.caspio.com/tech-tips-and-articles/tech-parameters/how-to-create-a-one-to-many-relational-datapage/

[pmcfarlain]

I'd prefer to keep it unique as these tables should be one-to-one rather than one-to-many but if I need to change it to make this work that's not the end of the world. However, even after turning off unique on the child table, I'm still getting the same error message.