Skip to main content
Submitted by Suzanne Scanlan on 17 January 2020

ArcherPoint Dynamics NAV / Business Central Developer Digest - vol 276

The NAV community, including the ArcherPoint teArcherPoint Dynamics NAV and BC Developer Digest Blogchnical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of  sharing helpful information with one another to help customers be more successful.

As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.

Developer Tip of the Day: Run an XMLPort Directly

Kyle provides another Developer Tip of the Day: “XMLPorts are flaky in BC14 and BC15 when importing. In code, if you run an XMLPort directly: 

Xmlport.Run(50000) 

It will (inconsistently) either not run at all, give false schema validation errors, or the dreaded ‘your file is too large’ message. Sometimes. Sometimes it works. Sometimes it will work in your local Docker container, but will give weird errors on the customer server. Use an Instream instead and it behaves a lot more predictably: 

InFileName := 'c:\share\ARC User Security.xml';  
InFile.Open(InFileName);  
InFile.CreateInStream(InFileStream);  
Xmlport.Import(Xmlport::"ARC User Security Import", InFileStream);  
InFile.Close; 

Docker Image Fail on Windows 1809

Bill Warnke advises: “If you're still on Windows 1809 and using process isolation, the 15.2 Docker images will fail, giving this message:

Service 'Dynamics 365 Business Central Server [BC] (MicrosoftDynamicsNavServer$BC)' cannot be started due to the following error: Cannot start service MicrosoftDynamicsNavServer$BC on computer '.'. 

Use HyperV isolation to get around the problem.” 

Best of Recent MS Dynamics 365 Business Central Blogs

Here are some quick links to recent helpful blog posts for D365BC and Dynamics NAV developers:

If you are interested in Dynamics NAV and Business Central development, be sure to see our collection of NAV/BC Development Blogs.

Read the "How To" blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.

Blog tags