Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
The purpose of this blog post is to demonstrate how we can achieve data filtration through Extensible Data Security (XDS) policies which cannot be achieved using Role-Based Security (RBS).
Dynamics 365 for Finance and Operations
This blog post uses Microsoft’s demo company data to demonstrate the concepts and processes and hence therefore doesn’t violate any data confidentiality policies.
In D365FO, Financial reports are stored in FinancialReports table in AxDB unlike in AX 2012 where they used to get stored in the reporting database and could be filtered per user through report library permissions feature in Management Reporter. However, we still can filter financial reports per user using the XDS policies.
Consider we need to configure security for a user such that he/she could only see reports under Housing Reports folder.
Create a query. Add FinancialReports table as a data source. Add range for field Folder. Set value to Housing Reports.
Create a security policy. Set the properties as highlighted. Please note that we are using RoleProperty as ContextType. Further we are using the primary table, FinancialReports as the constrained table as well. That’s why, we are not adding any other constrained table to the policy. Lastly, set the query to the one created above.
Create a new security role or use an existing one to update the Security policy context string value to the context string value we used on the security policy. This binds the security policy with the security role and eventually to the user.
Make sure the role has relevant duties to maintain or view financial reports.
Login with the user which is assigned this security role and bingo see the magic! Only reports under Housing Reports folder are accessible to this user.
Business Applications communities