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, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View 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 | Talent TechTalks | Upcoming TechTalks
A user with Global access level on the following is not able to create a report:
The user gets the following error when clicking NEW:
Record UnavailableThe requested record was not found or you do not have sufficient permission te view.
This may help - www.resultondemand.nl/.../source_sec_rpt.htm
Did you create a new security role from scratch ?
I hope this helps. If my post answers your question, please mark as "Verified"
Unfortunately, both posts above didn't help to solve this issue.
I created a new security role from scratch for test. I assigned exactly the same privileges for reports as the existing role. And it works with the new security role.
When I remove the new security role, it does not work anymore.
This is very strange.
Could some one explain the prvCreateReport privileges here https://msdn.microsoft.com/en-us/library/gg309380.aspx
the prvCreateReport is the privileges needed for the CreateRequest message. The exact set of privileges needed depends on the entity.
please refer this:
Hope this help!
READ Privilege on Publisher was the issue. Change the Read Privilege on the Publisher Entity to Entire Organization fixed the issue.
Business Applications communities