Posts

Request not supported new_xxx when calling Custom Action via WebApi

Image
Using CRM 2016 Online, you can create custom Action to execute custom business logic to meet your specific business requirements leveraging the workflow-like configuration window to define the business logic rather having it written in the code. The custom Action can be called via CRM WebApi, and I encountered the following error whilst working on one of the projects. 'Request not supported new_xxx' Whilst there could be different causes to the error, one that occurred in my case is because the Unique Name has been changed after it was created. The initial name was too long, hence, shortened afterwards. However, the new name is not re-generated in the API metadata. Rather than re-creating the custom API, you can find the original name before it was updated by inspecting the API metadata which you can view at the following Url. https://[organization uri]/api/data/v8.0/$metadata   Simply download the file and open in a text editor, you can search for the custom Act
Post a Comment
Read more

Field Security Profile Error

Seems to be a bug with Dynamics CRM 2013 (On Premise UR3), Field Security Profile Error occurs when user creates/saves new record by clicking on Save button, then saves more changes to the record while remain on the same screen. The error does not occur on subsequent updates if the user navigates away or closes and reopen the record. The entity has a field level security enabled field of Two Options field type, and a custom form with the custom field placed on the form. The user does not have any access to the field, and uses the form which does not have the custom field. User will receive similar error as per below: Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=6.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: User with ID 04b6b312-7d65-e411-82f6-005056a03354 does not have Update permissions for the new_securefield attribute in the account entity. The accountid of the record is f919
Post a Comment
Read more