Skip to main content

Solution to 'The request was blocked by the runtime to prevent accidental use of production services' error while making HTTP Call in Business Central

Introduction:

Recently, I have been working with Business Central's Http related Data Types.
In on esuch requirement where I had to make a POST call with JSON content. I'm sure that everything I was doing is perfectly fine and yet I get this weird error from Business Central while making an HTTP call to third party APIs

Error says:

'The request was blocked by the runtime to prevent accidental use of production services' 
Error: The request was blocked by the runtime to prevent accidental use of production services
Error: The request was blocked by the runtime to prevent accidental use of production services

Pre-requisites:

  • Understanding how APIs work.
  • Understanding of AL Language.
  • VS Code
  • Microsoft Dynamics Business Central

Books & References:

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/httpcontent/httpcontent-data-type

Solution:

I have worked with multiple API calls from Business Central to 3rd Party softwares and they almost always worked such as this one Generate Hash Value and Integrate Form Data Third-Party System using API Object.ystem using API Object
I suspect that this issue has been introduced in BC v16 and above although I don't have a clear conclusive proof at the moment.

I'm sure about the API call code that I have written as it is a standard code from Microsoft linked HTTP Data Type Example

Finally I discovered that in Extension management, click on the Assist Edit of the Extension having this HTTP Call and select Configure.

Extension > Assist Edit > Configure
Extension > Assist Edit > Configure

Enable the Allow HttpClient Request 
Enable Allow HttpClient Request
Enable Allow HttpClient Request

Although this boolean has been there for a while, I think that the validations behind this have been added recently.

Conclusion:

Before you assume that your code is wrong and searech for a new code, always DEBUG and look around.
Microsoft definitely and secretly keeps adding things to make the product more stable and mature. Although everything cannot be well documented, hence the true purpose of this blog.

Hope this helps.

Cheers

Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe