Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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
I need to restrict the portal user to view its own record only, Leads for example.
whatever Scope i choose it doesn't work but the global one only.
is there any missed step or anyone could guess what is the problem please.
Please checkout the below link:
are you selecting the correct relationship when setting up the entity permission?
are you clearing the cache?
are you associating the "authenticated" web role against the entity permission ?
You have to look in those areas:
1. Create Entity Permissions with "Contact" Scope and choose the relationship between the lead and contact that is used to display the leads in the portal for that contact
2. Assign the needed Web Role(s) to that entity permission
3. Enable entity Permission on the entity List record of the leads
4. Make sure that the contact has the appropriate Web Role added to the entity permission
Business Applications communities