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
I am in the process of accessing Data entity through OData which is marked as Private. I done the below steps.
1) Create a copy of the entity by clicking on 'Duplicate in project'.
2) Rename the entity and set the property 'IsPublic' to Yes; Set value for Public Collection Name and Public Entity Name
3) Build the project.
During build below error occurred which I don't have any clue. Please help
Error BP Rule: DataEntitySecurityPrivilegeCheck:Path: ..... The data entity 'CITShipmentHeaderEntityCopy' is not assigned to a security privilege.
The data entity must be associated with a security privilege.
Look at the entity which you copied - right click - Find references and you will see what it looks like.
Create view and maintain security privilege for the new data entity and assign it to entity.
If you create entity through wizard privileges are created automatically . Because you duplicated entity , you have to create those manually and assign it to entity.
Note that the "error" is not an error, but rather a BP Error. So technically you can still ignore it. (You can even build a deployable package.) Go to VS options -> Dynamics 365 -> build -> turn of BP checks. Then you will no longer get the "error".
I find it a bit irritating that MS decided to make this a BP Error, I mean it is a BP violation, but not an error. MenuItems without privileges don't give you a BP error, but only a kind warning - which is a very helpful reminder. (end of rant)
Turning of BP checks is not a good idea (I just mentioned it to explain). Like mentioned already - you can solve the issue by doing what the BP error is complaining about. Create a privilege and assign the entity to it. You will probably get another BP error after that, which you can fix by specifying the Grant property on the DE node in your privilege.
Thanks. I successfully exposed the entity now.
Business Applications communities