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 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
When browsing to the Associated Opportunities in an Account record I receive an error above the grid (which is set up as an Editable grid since it is enabled on the Opp entity in my org) and no Opportunities are shown. There is a red X and an error which states "The feature is not supported in the current version of the product" (Dynamics 365 with the December '16 update). If I switch the view to use the Read-only grid the error goes away and the Opportunities are listed as expected. What gives?
For what it's worth.. does not work for me either. Contacts associated view editable grid works just fine, though. Seems to be a problem with opportunities.
The Editable Grid currently only works with grids that are backed by plain FetchXML queries. This is not a problem for custom entities and the large majority of supported legacy entities. Now, if you look closely, the Filter / Include panel you see right above the command bar is a feature only available in a few out-of-the-box entities such as Opportunities and Cases.
Unfortunately, in both Opportunity and Case Associated Views, the filter option "Include: Related 'Regarding' Records" requires special processing by the data layer to work hence the error message you see. On the other hand, the options "Include: This Record Only" and "Include: All Affiliated Records" work fine.
Just as a curiosity, the in the Accounts entity, the view "Accounts: No Orders in Last 6 Months" is also unsupported due to the same limitations.
So if I change the filter to "Include: This Record Only" I am able to view the related records and the error goes away. Is there a way to default this? I'm not sure I really understand the difference between the two but as long as it shows the associated Opportunities I'm OK with it.
Short answer: As far as I know, the "Filter / Include" panel is not customizable as of now. Keep in mind that the default option is a legacy behavior and it may be confusing to have different defaults for editable and standard grids (or across different Dynamics 365 organizations).
Long answer: Here's the explanation detailing what each "Include" option should do:
A rollup record is not requested. This member only retrieves the records that are directly related to a parent record. Value = 0.
A rollup record that is directly related to a parent record and to any direct child of a parent record. Value = 1.
A rollup record that is directly related to a parent record and to any descendent record of a parent record, for example, children, grandchildren, and great-grandchildren records. Value = 2.
account or contact
Related, Extended, None
Thank for the thorough explanation Pedro.
I guess what I am not understanding is why is this View different from other entities (Alex already mentioned Contacts) and particularly Custom entities?
And additionally, how do workaround it? I'm considering setting up a second 1:N relationship to add to the Navigation section to see if I get a different view.
I believe the ability to perform rolled up queries was not meant to be available for any entity in Dynamics 365, maybe due to fears of performance impacts. Therefore, Microsoft picked only a handful of entities to support. Opportunities and Cases have support while Contacts or custom entities don't.
You idea of a new relationship is interesting. Let me know how it goes.
Is there a way to change this in unsupported way in DB maybe or JS?
Business Applications communities