kjoseph 2008-06-19T11:43:53Z Changed status to <span class="status_tag">Delivered</span>. rich_r. 2008-04-24T06:46:03Z So does this mean that when creating a contact to contact relationship, I will no longer have to use an s-control to display the relationships on the contact layout; or alternatively use two related lists on the object. Please advise so I don't spend too much time developing these s controls. Thanks. ToddJanzen 2008-04-21T14:52:48Z I think this would solve my idea as well: http://ideas.salesforce.com/article/show/26498/Contact_to_Contact_Relationships hpPMO 2008-04-15T05:50:48Z Is this same as : http://ideas.salesforce.com/article/show/10079268/CrossObject_Formula_Fields_Be_able_to_insert_related_Object_data_into_a_formula_field? EricB 2008-03-31T13:03:33Z Changed status to <span class="status_tag">Coming in Summer 08</span>. Tom_Tobin 2007-12-19T10:12:41Z The junction objects can be a detail of one side, which is often enough - a test drive object linking a car to a customer shouldn't go away when the car is sold... but might go away if the customer is deleted. The best option right now is to use Apex or SControls to create the junction object and the item on the far side from one form - allowing the user to not have to worry about the complexity, and build a CRT to let them report over the junction. Having M:M would not work well in many situations, and would complexity the security and related-list and join management a lot, and would only be really useful for when there is no information on the join itself. If there is information to keep in fields on the join, then you need an object in the middle anyway. xactandy 2007-12-19T00:08:33Z A bigger issues is deletion of dependent relationships. So if you have a many to many between two objects, and you delete one of the objects, then the dependent relationship should be deleted as well. The only way to do this is Apex or an S-Control. AlexCRMmanager 2007-12-18T15:04:01Z I agree with Toddb - the way we have to implement Many-Many relationships is Salesforce.com often ends up being rather ugly and un-user-friendly for the end user. Salesforce.com needs to make the process of creating a Many-Many relationship more streamlined for the developer, and simpler for the end user. We need to be able to create things like Contact Roles without have to do a lot of custom code to make the interface nicer and easier for the end user. Tom_Tobin 2007-12-12T17:11:27Z Custom Report Types will work for 4 children of the primary object. But often, you can choose the primary object. From the primary object, you can follow lookup relationships up to 4 steps away - looking up the great-great-grandparent. curth 2007-12-10T09:29:10Z I support the idea that Salesforce.com needs to make it easier to create many to many relationships and include those relationships in reports. In addition, Custom Reports only works if you are reporting on object, parent object, grandparent object, etc. It is not well suited for reporting on grandparent, parent, and 2 grandchildren objects. Tom_Tobin 2007-12-06T20:54:16Z you can go back up. In the "Edit Layout" page, choose the object you want to go back up from, and click "Add fields available via lookup". Or read the 2nd half of the blog post, which says the same thing. toddb 2007-12-06T20:04:50Z The link above is bad. Try this https://na3.salesforce.com/servlet/servlet.ImageServer?id=01550000000IIVu&oid=00D500000006imU toddb 2007-12-06T18:45:54Z I've uploaded a picture to help explain the problem. https://na3.salesforce.com/servlet/servlet.FileDownload?file=01550000000IIVu If report types will work, that would be great. I'm not sure if they will. report types work on a tree that has multiple parent->child->child relationships. With report types you can not go from parent to child then back up the tree to another parent....Correct??? Also, I was talking with another consultant on our team and he mentioned it would be great to have "Roll Down Fields" for any relationship (not just master-detail). This would allow the linking of mutiple objects and allow fields/data to be present in the linking object forming the composite view. This would also allow other fields to be added to linking object making it more generic and useful. Tom_Tobin 2007-12-06T17:17:47Z I don't understand what you want to list in a listview? Wouldn't it be better if listviews and related lists could be based off a CRT and you could go lookup any field you wanted? Scott_Jorgensen 2007-12-06T17:17:47Z If you define a Custom Report Type you can report across your many-to-many relationships. Also, if one of the relationships is a Master Detail and another is a Lookup then you'll get a standard report automatically the spans the many-to-many relationship...no need to make a Custom Report Type. Tom_Tobin 2007-12-06T17:17:47Z Why not use Custom Report Types? http://blogs.salesforce.com/analytics/2007/10/hiding-or-polit.html