We recently combined several custom object into a single object to simplify the model. But I still have the requirement of a many to many relationship within this object. I assume I need a junction object, but when I tested I ended up with 2 identical related lists on the object (via 2 lookup fields on the junction object pointing to the same object). Any thoughts? Thanks!
10 answers
I'll try to answer with example:
Let say we have child object A that has lookup field F to the master object B.
Only on master object B there will be a related list of A (of field F). Nowhere else. By default the name of related list on B is set, however you can change the name of the related list by editing field F.
Now, let say we have on object A second lookup field F2 to master object B. Again on B there will be new related list of A (of field F2). Related list of F & F2 are "not connected" and are treated as separate entity.
Let say you now have for records.
recordB
recordA1 that has field F=recordB, F2=<blank>
recordA2 that has field F=<blank>, F2=recordB
recordA3 that has field F=recordB, F2=recordB
recordB related list 1 (A-F) will show:
recordA1
recordA3
recordB related list 1 (A-F2) will show:
recordA2
recordA3
