I need some help here. Here is part of my data model:

I have folder, but I also want to have some folders that I can access easily without searching each time. So I made a default folders entity and I want a relationship to a certain folder.
However, it’s complaining that it wants a reverse relationship. I don’t see how that would work in this case. Any ideas?
Ramy’s answer is correct, you don’t have to define an inverse relationship. I just want to point out an alternative:
You can define multiple inverse relationships from
FoldertoDefaultFolders, e.g.defAccountas inverse relationship toaccount,defArchiveas inverse relationship toarchive,Disadvantage: The
Folderrecords are larger, so your database needs more space.Advantage: If you define the “Delete Rule” as “Nullify” for these inverse relationships, then the
account,archive, … properties inDefaultFolderswill be set tonilautomatically if the correspondingFolderis deleted.