In the previous post, we created a simple custom API https://nishantrana.me/2021/01/13/use-custom-api-to-create-custom-messages-in-dynamics-365/
Let us look at its different properties starting with ExecutePrivilegeName
Execute Privilege Name attribute of custom API allows us to specify the name of the privilege that allows execution of the custom API.
Let us update the custom API and specify the privilege name.
For simplification, we have used prvCreateIncident here i.e. Create Case / Incident Privilege.
To get the Privilege name
https://%5Borgname%5D.api.crm.dynamics.com/api/data/v9.1/privileges?$select=name
To test, we updated the security of the Application User to Sales Manager role which doesn’t have the create incident privilege.
Calling the custom API this time as expected gave us the below error
{“error”:{“code”:”0x80040220″,”message”:”Principal user (Id=0f377e29-5545-eb11-a813-000d3a9bf733, type=8, roleCount=1, privilegeCount=727, accessMode=4), is missing prvCreateIncident privilege (Id=6cf9442b-e690-4cad-8b0a-e60464960b93) on OTC=112 for entity ‘incident’. context.Caller=0f377e29-5545-eb11-a813-000d3a9bf733″}}
If we specify an incorrect privilege name we would get the below error and will not be able to save the record.
Hope it helps..
Advertisements
- Unable to Delete Work Order Due to “The Time To Promised Must Be Later Than The Time From Promised” exception – Dynamics 365 Field Service
While attempting to delete a historical Dynamics 365 Field Service Work Order, we encountered the following error: Exception Message: The time to promised must be later than the time from promised. ErrorCode: -2147220891 HexErrorCode: 0x80040265 Error Details: {“errorCode”:2147746405,”message”:”The time to promised must be later than the time from … Continue reading “Unable to Delete Work Order Due to “The Time To Promised Must Be Later Than The Time From Promised” exception – Dynamics 365 Field Service” - Open a Power Automate Flow for Edit Without Fixing Broken Connections First
While reviewing Power Automate flows recently, we ran into an issue where we could not open a flow in edit mode When opening the flow, Power Automate displayed the “This flow will connect to” screen and requested that we fix one or more connections before proceeding. In our … Continue reading “Open a Power Automate Flow for Edit Without Fixing Broken Connections First” - Dataverse Web API: Returning Record Data During Create Using Prefer: return=representation
When creating records using the Dataverse Web API, the default behavior is to return a successful response without including the record data in the response body. A standard create request does provide access to the newly created record’s GUID through the OData-EntityId response header. However, if we need … Continue reading “Dataverse Web API: Returning Record Data During Create Using Prefer: return=representation” - Testing the New RunJobForSandbox Option in Bulk Delete Jobs (Preview) – Dataverse / Dynamics 365
Microsoft recently introduced a preview feature for Dataverse Bulk Delete Jobs that provides additional control over bulk delete processing. One of the new options available when creating a bulk delete job through the API is RunJobForSandbox. According to the documentation, this option is intended to control sandbox processing … Continue reading “Testing the New RunJobForSandbox Option in Bulk Delete Jobs (Preview) – Dataverse / Dynamics 365” - Using RetrieveDependenciesForDeleteRequest to find and delete hidden dependencies (Dataverse/ Dynamics 365)
Please refer to the post below, which provides a clear explanation of how RetrieveDependenciesForDeleteRequest works and how it can be used to identify dependencies. Discover more from Nishant Rana's Weblog Subscribe to get the latest posts sent to your email. Type your email… Subscribe - Troubleshooting Hidden Dependency Errors in Dynamics 365 and Dataverse
Recently, while cleaning up some old customizations in Dynamics 365, we came across an interesting dependency issue that was not immediately obvious from the user interface. What initially looked like a simple Business Process Flow deletion turned into a deeper investigation into how Dataverse manages published dependencies internally. … Continue reading “Troubleshooting Hidden Dependency Errors in Dynamics 365 and Dataverse” - Capture UTM Parameters in Dynamics 365 Marketing Forms Using JavaScript (Dynamics 365 Customer Insights)
When running marketing campaigns, UTM parameters help us understand where our leads are coming from. They help us track whether a lead came from Google Ads, Facebook campaigns, email campaigns, or some other source. Recently while working with a Dynamics 365 Marketing form, we used a small JavaScript … Continue reading “Capture UTM Parameters in Dynamics 365 Marketing Forms Using JavaScript (Dynamics 365 Customer Insights)” - Hidden Required Fields Causing “Please ensure all required fields are filled out” Error While Disqualifying a Lead in Dynamics 365 / Dataverse
While working on a Lead Disqualification scenario in Dynamics 365, we ran into a strange issue. When trying to Disqualify a Lead, Dynamics 365 was showing the generic error message: “Please ensure all required fields are filled out and have valid info.” Even more confusing, the form itself … Continue reading “Hidden Required Fields Causing “Please ensure all required fields are filled out” Error While Disqualifying a Lead in Dynamics 365 / Dataverse” - Preserving ‘modifiedon’ During Data Migration in Dynamics 365 / Dataverse
We were working on a data migration requirement where we needed to preserve system fields like created on and modified on. For Created On, things are straightforward. We can use the overriddencreatedon field, something we had already explored earlier here: https://nishantrana.me/2018/10/16/using-overriddencreatedon-or-record-created-on-field-to-update-created-on-field-in-dynamics-365/ In this post, we focus on preserving … Continue reading “Preserving ‘modifiedon’ During Data Migration in Dynamics 365 / Dataverse” - Reset / Restore the standard (OOTB) button in Dynamics 365 / Dataverse
We recently worked on a requirement where we customized an out-of-the-box ribbon button in Dynamics 365 — specifically, the Reactivate Lead button. We had renamed it to ‘Reactivate’ as part of an earlier customization. Below is how the button appeared on the form after customization: Later, we had … Continue reading “Reset / Restore the standard (OOTB) button in Dynamics 365 / Dataverse”
Discover more from Nishant Rana's Weblog
Subscribe to get the latest posts sent to your email.
Share It -
Nishant Rana's Weblog 
4 thoughts on “Execute Privilege Name (ExecutePrivilegeName) property of Custom API in Dynamics 365 / Microsoft Dataverse”