Hello reader,

If your Business Central extension makes outbound API calls and one day they all stop working with a cryptic error like the one below, this post could save you days of troubleshooting. It cost me plenty of time before I found the culprit, and the fix took less than a minute.

You get an error like this

The Symptom

An integration that has worked for a long time fails out of nowhere. Nothing in the code changed. The same request works perfectly when you send it from Postman, but from Business Central, HttpClient.Post() simply returns false. No HTTP status, no response, no useful log entry. The request never leaves the service tier.

The Root Cause

The "Allow HttpClient Requests" setting on the extension is turned OFF.

Every extension in Business Central has a per-extension permission controlling whether its AL code may make outbound HTTP calls. When it is off, every HttpClient call fails instantly and silently. The nasty part is that this flag can silently reset when the extension is re-published or upgraded, or when the environment is copied or restored. So a routine deployment quietly kills your integration, and the failure looks like an external API problem.

The Fix

1. Search for Extension Management
2. Locate your extension and open its details (or ... menu, then Configure)
3. Switch Allow HttpClient Requests to ON
4. Retry. No restart or re-publish needed

Lessons Learned

• After every publish or upgrade, verify the flag. Make it a deployment checklist item.
• Test the same request from Postman. If it succeeds outside BC but fails inside, suspect this flag before blaming the external API.

Business Central/NAV ERROR A server was not found at "net.tcp://localhost:__/ChromiumTEST/Service". Either the URL is incorrect or the server is currently not available.

I noticed that issue could be resolved by changing the service account login to Admin user account.

Access Business Central running inside Virtual Box over the internet(Host must have public IP)

 Hello reader,

It took me sometime to achieve the request.

Generally you have a physical server with a public IP. The server could be running many other services.

In my case the server is running an older version of windows server.

So i installed a Virtual Box with new windows server and install Business Central there.

But getting Business Central to be accessible to outside network over the internet is the trick.

If that is your problem then you are in the right place.

I assume you have already installed business central in the VM and it is running

Procedure

Setup Bridged Network to all VM share host’s internet/network

• You need to first switch off the VM
• Select the VM inside virtual box menu
• Select settings
• Select Network
• Select adapter 2
• Make sure network is enabled
• Select Attached to  = Bridged Adapter
• Select appropriate adapter in the name
• Click ok to save

 This step is well explained here

Setup the VM to use static IP address

• This is the usual process done in the network section

 

Configure Port forwarding between VM application & Host machine

• This is done using the NAT network on adapter 1
• Go back to where you setup the abridged network. 
• Select adapter 1
• Select Port forwarding
• Map the host/physical computer IP address(Local IP) to VM static IP set in preceeding step
• Map the port number for accessing Business Central in VM to a chosen port on the Host
• Make sure those ports are allowed through the VM firewall settings

 

Configure port forwarding on the Router and firewall for external access. This is done on the Host Network. It also depends on the firewall/router you are using.

Good luck

ERROR Changing Business Central to NAVUserPassword Authentication "login failed for user 'NT Service\SSISScaleOutMaster150'. Reason: could not find a login matching the name provided [CLIENT:]"

 

Hello reader, I got the above error while attempting to change my Business Central to use NAVUserpassword authentication.

I have gone through the procedure as described by Microsoft BC Manual

However the error kept on persisting. I had to do many things, i cant tell really what worked exactly.

• First ensure you -> Grant access to the Business Central Server service account. You may read for more on this process.
• Make sure NT NETWORK SERVICE & your WINDOWS ADMINISTRATOR(If this is the default account you use to login to your business central database instance) account has full access to your Business Central Database.
• Restart your Business Central Service

That should solve your problem hopefully.

ERROR installing windows server 2019 in Virtual Box "windows cannot find the Microsoft Software License Terms.Make sure the installation sources are valid and restart the installation "

ERROR -windows cannot find the Microsoft Software License Terms.Make sure the installation sources are valid and restart the installation 

Am not sure what caused the problem but various individuals on Microsoft Community say different stuff. 

Here is a solution that worked for me

It's possible the media is corrupt in which case I'd try downloading from another location to avoid the same copy ISP has cached on their systems. some hypervisors such as VMWare add an additional floppy drive that causes install media to look for licensing on floppy, in this case remove the virtual floppy from guest and try again. Also try;
Bypassing Easy Install

• First start VMware Workstation
• Create A New Virtual Machine
• Select the option “I will install the operating system later”
• Then your new virtual machine will be added to your virtual library.
• Double click on your new Virtual Machine to start it.
• Then it will prompt that an OS is not installed and provide an option to insert the OS installation media.
• Simply click on Change CD/DVD Settings to select your ISO media then Restart VM.

Good luck

"Unveiling the Mystery: Forex Revaluation Entries Posted Outside End-of-FY in Business Central - What Could Be the Reasons?"

 Hello reader,

I encountered the above problem when i ran forex revaluation.

Certainly! Here are two key points to address the issue of invoices applied to post-FY payments/receipts in Business Central:

Issue: Invoices falling within the previous financial year were paid and applied to payments/receipts posted after the financial year ended, leading to discrepancies in financial reporting.

Solution: Un-applying the receipts and payments. By reversing the application process, we can remove the linkage between the invoices and the post-FY transactions, ensuring accurate financial records

Action Steps:

a. Identify the invoices that were applied to post-FY payments/receipts and determine the correct financial period they should be associated with.

b. Un-apply the affected receipts and payments associated with those invoices. This will detach them from the incorrect financial period.

c. Re-apply the receipts and payments to ensure they are correctly assigned to the appropriate financial year, maintaining accurate financial reporting.

By following these steps, we can resolve the issue of invoices applied to post-FY payments/receipts and ensure the integrity of your financial data in Business Central. If you require further assistance, don't hesitate to reach out for support.

Why the fields you added to the child extension in business central do not show in the parent extension using AL

Resolving Field Access Issues in Parent Extensions for Microsoft Dynamics 365 Business Central

Introduction: As a Business Central developer, it is not uncommon to encounter challenges when working with extensions, particularly when accessing fields in child extensions from parent extensions. In this article, we will address a common issue where newly added fields in a child extension are not accessible in the parent extension. We will provide a solution to ensure smooth integration and seamless access to these fields within the parent extension.

Solution:

1. Update the Child Extension Version: To begin, it is crucial to update the version of the child extension in the app.json file. For example, if the current version is 1.0.0.0, increment it to 1.0.0.1. This version update ensures that the latest changes are recognized and applied throughout the system.

2. Update Parent Extension Dependencies: Next, update the dependencies in all parent extensions to reflect the new version of the child extension. This step establishes the necessary connection between the parent and child extensions, allowing for proper integration and field access.

3. Compile, Package, and Publish the Child Extension: After updating the version and dependencies, proceed to compile, package, and publish the child extension. This step ensures that the extension's changes are properly bundled and deployed for use in the Business Central environment.

4. Download Symbols in Parent Extensions: To enable seamless communication between the parent and child extensions, it is essential to download symbols in the parent extensions that have a dependency on the child extension. Symbol downloading facilitates the recognition and utilization of the updated fields.

5. Package and Publish the Parent Extension: Finally, package and publish the parent extension, incorporating the changes made in the child extension. This process allows the parent extension to recognize and access the newly added fields successfully.

Conclusion:

By following these steps, you can resolve field access issues encountered when working with parent and child extensions in Microsoft Dynamics 365 Business Central. Remember to exercise caution and perform these operations on a test environment before applying them to a production environment. Maintaining a comprehensive backup of your database is also crucial to mitigate any potential risks associated with these modifications.

As a Business Central developer, it is essential to be equipped with the knowledge and expertise to address these types of challenges. By implementing this solution, you can ensure a smooth and efficient integration of extensions, enabling optimal functionality within the Business Central environment.

Good luck!!