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.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
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
I have created a campaign form that (somewhat like a dashboard) allow us to spawn opportunities directly and associate it with a campaign it belongs in, notably in that very form. I can easily add the subgrid and can add directly from the grid and see that data but the Associated Review button is missing. The screen shots attached show that I have a 1:M relationship that is included but it doesn't seem to work.
In the subgrid, I have set to Opportunities (Source Campaign) to show the association. If I move to Opportunities (Related Records) I get the grid icon but none of my records are visible. Obviously the relationship that the grid recognizes is (related records) but how do I get (source campaign)?
Carolina Financial Securities LLC
Investment Banking | Member FINRA, SIPC
when you use on subgrid these settings:
Records: Only related records
Entity: Opportunities (Source campaign)
..it will not show up associated review button. I had same problem and i don't know why this happening, it looks like bug. Somebody else wrote about it too here:
So if you want to show that button it's possible if you create new relationship between Campaign/Opportunity and use this for set up on subgrid like:
Entity: Opportunity ("Customized" Source campaign)
With this you should create new lookup at Opportunity form and thats all. Associated review button will be on.
I tried the same on my test org and it worked as expected. Below are my subgrid properties. Ensure that you have opportunities with the source campaign field populated with that campaign.
Hope this helps.
what is your version of CRM on tested org? I test it on version CRM 2016 184.108.40.206 with same subgrid properties as you show and as i wrote i had same problem as Ed, that's why i used that workaround.
I appreciate you sending those settings. It does look like we are on a different version but I did verify the settings are the same.
My version: Microsoft Dynamics 365
Version 1612 (220.127.116.11) (DB 18.104.22.168) on-premises
I have seen some discussions of this being a bug which is unfortunate.
I am running:
Microsoft Dynamics 365
I tested on V9.1 trial. I guess you are correct, as it is happing on multiple org with the same version then it is most likely a bug and cause its working in v9.1, I can assume that this bug is fixed.
So we can upgrade to v9.1 or anyway use that workaround which i wrote with custom field cause that's work well - i didn't saw any disadvantages yet of not using native field (Source campaign).
Thanks for the review.
I would not recommend a workaround as by January 31 everyone will be default upgraded to V9.
Business Applications communities