Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Customer Service updates!Learn about the key capabilities and features of Dynamics 365 Customer Service and experience some of the new features.
Download overview guide | Watch Customer Service video
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Here's the setup. I have two custom entities: Patient and Encounter
One patient can have multiple encounters so I created an N:1 relationship between Encounter->Patient.
Encounter has a field called location. I'd like to display this field in a Public View from Patient. When I select Add columns, I don't see any option to add a value from Encounter. I searched for similar issues but it seems like the only questions are asking about the opposite situation, showing parent values on a child entity.
Any tips here are much appreciated.
As you have mentioned that one patient can have many Encounters which means each Encounters will have its own value for the field location. Then how can you show multiple values in a single value. This is the reason you cannot select the fields from child entity.
Assume the below sample data. In this P1 is associated with E1,E2 & E3 and all these have there own location value i.e L1,L2, L3. You cannot display multiple values in a single field in a view unless you are creating your own custom html web resource and concatenating the multiple values.
P1 E1 L1
P1 E2 L2
P1 E3 L3
Hope this helps.
Yes that makes sense. I forgot to mention that there can only be one active encounter row associated with a patient. I use a status code on Encounter to mark encounters as active or inactive. I think I should probably try and make a view from the child entity that is active in this scenario.
Thanks for looking into this.
It doesn't matter how many records you have in child entity. If the relationship is 1:N then you can not display the child fields in the parent entity view.
Business Applications communities