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.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 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
For our community portal I have created a n:n relationship between contact and a custom entity named themes. Here users can, trough a subgrid placed on an entity form available on their profile, show interest in several themes we as a community discuss.
Now I want to fetch all themes a contact is interested in trough this n:n relationship in a liquid fetchXML to create a customised welcome screen for the user on the portal. This themes entity is used trough out the portal so I like to have it as a relation.
in XRM toolbox I was able to build a fetchXML statement to query the needed data. However when on the portal this query does not work. Is it possible to query n:n relations this way? Entity permissions for both entities are set to global read. Is there any other way to fetch the required data? I need the name and guid of the related themes to a contact.
thanks in advance.
the xml statement:
<fetch top="50" > <entity name="contact" > <attribute name="firstname" /> <attribute name="lastname" /> <link-entity name="bhs_contact_bhs_thema_final" from="contactid" to="contactid" intersect="true" > <link-entity name="bhs_thema" from="bhs_themaid" to="bhs_themaid" alias="thema" > <attribute name="bhs_name" /> </link-entity> </link-entity> </entity></fetch>
How exactly you are displaying retrieved data? fetchxml on the portal behaves a bit differently than regular fetchxml. To retrieve data from the second level link entity (like in your case) you should just call an alias of that link entity as it was the first level.
results['thema.bhs_name'] - should return necessary value
When you set up the Entity Permissions, you need to use a scope where you chose the relationship between the two entities e.g. Parental (just setting Global at each end of the relationship won't give permission for the system to traverse the relationship/link-table between the 2 entities).
Business Applications communities