Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We are using the Lead entity and have a OneToMany relationship from it to the Opportunity entity. However, we don't actually consider the Leads "parents" of Opportunities because we do not create Opportunities from Leads; Opportunities are created in our own in-house system and then interfaced into Dynamics CRM. To associate the records together, we have a subgrid on the Lead form to show related Opportunities, and then just use the "Add Existing" button on the subgrid to link one Lead to many Opportunities.
Once that relationship is created using the "Add Existing" button, a user can then NOT "Remove" the record because there is no Remove button on the subgrid. From my research, that appears to be intentional functionality due to it being a OneToMany relationship--Microsoft's logic being "this is a parent-child relationship, you can't have a child without a parent." Which is valid, but doesn't encompass our particular logic (which I argue is just as valid--from a business standpoint, it IS OneToMany because we do NOT allow an Opportunity to have multiple Leads, regardless of how the Opportunity was created).
Opportunities are NOT writeable because they come from our in-house system, which is considered the authoritative system. They cannot be edited in Dynamics CRM.
So if a user creates a relationship from a Lead to an erroneous Opportunity, they have no way of deleting that relationship ("Remove record"), because there is no "Remove" button on the subgrid, and they can't go to the Opportunity and remove the lookup on that form.
Enable "remove" button on opportunity subgrid (This one looks a LOT like my exact scenario but there was no follow up that really helped.)
Custom button on subgrid dissappears incorrectly (The question is not quite what I'm asking, but the answers seem to suggest this IS possible? But I cannot get it to work using this method.)
I have made sure that the security role I'm using for this has Append To rights for the Opportunity entity, and Append rights for the Lead entity.
I found my answer.
It IS possible with OOB functionality that you just have to tweak. I had two issues:
1) I was modifying the Lead subgrid ribbon when I should have been modifying the Opportunity ribbon!
2) I didn't have the OrRule set to Default: True!
That did it for me!
Business Applications communities