Starting November 20, the site will be set to read-only.
On December 4, 2023,
Apex Code Development (90768)
General Development (55146)
Visualforce Development (37251)
Lightning (18265)
APIs and Integration (17146)
Trailhead (11680)
Formulas & Validation Rules Discussion (11337)
Other Salesforce Applications (8116)
Jobs Board (6655)
Force.com Sites & Site.com (4842)
Mobile (2694)
You need to sign in to do that
Don't have an account?
kdmr Hi,
I am i have a created a custom object and am trying to make a master-detail relationship with the object Product. The problem is when I select Master-Detail the Product object does not show up in the drop down list. Does this mean that I can not create a Master Detail relation ship keeping the Product as the master or is there some settings to be changed to get this done.
Thanks
KD
Did anyone ever contact you with this answer? I am having the same issue right now and cannot find a solution. Thanks
I am sailing in the same boat, please post any pointers you received.. thanks
Same issue here. Any updates?
I've encountered the same issue. Of course this was after I had already set up the child object. (in my case it's "Product Lot" which is like a batch of products with date & quantity details... obviously we want a total quantity on the Product... )
Looks like I will have to just use a regular lookup, and write a couple Apex triggers to handle the "roll-up summary" fields. Not a very elegant solution in my opinion.
I've love to know why a Product2 cannot be a master.
I wish we knew, when i was researching I did not find anything solid, just a SF documentation that said Product2 object cannot be the master.
If I remember correectly, I did call SF support , but they did not have any reason too.
I ended up creating new custom object.
I have read that any object can have only upto 2 Master-Child relationship, and my guess is that Product2 object already has 2 Master Child relationship.... I may be wrong and there could be some other reason.
KD119,
Well you are right on that any object can have atmost 2 masters. I do not see master child relationship on Product2 object itself. Are you referring to PricebookEnter object?
Also if an object has 2 master child relastionhip, it itself can be a master for some other object, master-child is always defined on the child object.
I think Product2 and few others are just exception for master-child, I may be wrong too, but so far I found nothing.
I have the same problem and am creating a new custom object too.
Being that the Product object's API name is "Product2", it sounds like at least one mistake is already being bandaged over. I would bet this Master-Detail is part of the same.
Also having same problem as we're expanding fuctionality of an existing system. Wish I could create custom object and start from fresh, but worried it mess with all the existing data. Going to go the look-up route. Is there someone from Salesforce.com who can explain why this exists this way?
Also having same problem as we're expanding functionality of an existing system. Wish I could create custom object and start from fresh, but worried it mess with all the existing data. Going to go the look-up route. Is there someone from Salesforce.com who can explain why this exists this way?
I don't think there is a limit of 2 on the number of times an object can be the master. Our Campaign object is the master to 9 custom objects.
Chris
cnoe26, you can have atmost 2 master detail relationship for a child object. I do not think there is a upper limit on an object that can be a Master object.
regards
SF Partner
I am stucked up on the same point. I have raised query to Salesforce. Hope will get some positive feedback.
Ditto. Having the same issue. Any ideas?
I ended up dropping Force.com and redeveloping on another platform.
When a question comes up like this a good follow up question is "why?"
In this case why do you want product to be the master in a master detail relationship?
M-D Relationships have several factors to consider:
1. They are always required.
2. The force inheritance of record access and sharing model from parent to child
3. By default they are not updatable (but as of Summer 12 can be)
4. They cascade deletes
5. They allow an admin/developer to use roll-up summary fields
All of these have work-arounds if you are compelled to use a lookup relationship. So which of these is standing in your way?
The issue is the ability of the framework (or lack of ability in this case) to support inheritance. A Master-Detail relationship is fundamentally an inheritance model that indicates the detail "is a" detail of the master. Since an object can have many lookup relationships, this is instead a "has a" relationship with respect to the lookup object, which means that you cannot model true inheritance. Although it may be possible to "work around" this massive limitation as you suggest, all such efforts are ultimately hacks..
From a practical perspective, it is unbelievably unwieldy to try to join objects into a single entity programmatically and the work-around strategy breaks down completely if you try to model multiple layers of inheritance such as vehicle->land vehicle->passenger vehicle->suv.