Request not supported new_xxx when calling Custom Action via WebApi
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