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 2 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
Within cases I have look-ups to 5 separate entities I have created.
These break down defects so Defect 1 lookup> filters lookup 2 etc....
what is the best way to set this up from a hierarchy point of view so that When I select an option on lookup 1 it filters what lookup 2 shows etc?
Will these also be able to be shown in a portal?
Why 5 separate entities? - you could use a single entity with a self-referential parent lookup field.
Then on your case entity the top (Level 1) lookup is filtered where the parent value is blank
And Levels 2 - 5 are dependant on the value in the previous lookup.
community.adxstudio.com/.../enhanced-crm-view-filtering says that it should work with portals
Agree with Ben, we should have created a single entity with selef referential relationship. Similar to what you have in account entity "Parent Account".
So you can have an entity called "Defects" and then within that entity create another lookup field called Parent Defect (lookup to self)
This should work for your.
Hope this helps.
Hi thank you- in this case the users want 5 entities to be able to update singularly each different defect without using 1 entity. If I were to create a self referencing entity how would i go about doing that Just creating a 1:N relationship with Cases to Cases?
How would I reference these so I have 5 entities Create a parent Lookup field on all:
1.Room (No parent)
2. Elements (Filters from Room selected) do I need to create a 1:N lookup to Room and label it parent defect?
3.Nature (1:N Lookup to elements)
4.Description (1:N to Nature)
5. Detail (1:N to Description)
How could I create a related filtered view> for the 5 entities ?
I managed to do this via "show only then using the lookup views"! Thank you both for your help
Business Applications communities