Skip to content

ArcherPoint Dynamics NAV Developer Digest - vol 229ArcherPoint's Developer Digest Weekly Blog

The NAV community, including the ArcherPoint technical 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.

Visual Studio Code: Using the Code Analysis Tool

Saurav shares these instructions for using the VSC code analysis tool, which will be helpful to ensure ArcherPoint coding standards are being followed when developing in MS Dynamics Business Central.

You’ll first need to enable code analysis, then add your code to the project. Read the post by Microsoft for all the details.

Developer Tip of the Day: Export and Backup Code When Using Docker Containers

Kyle agonizes when sharing this tip of the day: “Always, always, ALWAYS export and back up your code. I just lost hours of work because I refreshed a Docker container without making sure I had everything out that I cared about. One simple FOB save before I rebuilt the container would have prevented my pain.”

Developer Tip of the Day: Call an XMLport in AL

Kyle shares this tip on how to call an XMLport in AL. “This took me a bit of internet research and experimentation to get it working. In the new cloud / BC / D365 world, for security reasons, we are not given access to local file systems. So they had to come up with a different way to get files into an XMLport using a new function called UploadIntoStream.

I could not figure out how to get it to stop prompting - sometimes I know the filename and don't need a prompt, but UploadIntoStream insists that the filename variable be writeable. It prompts, and then returns you the filename you selected. 
 
codeunit 50099 "Temp Kyle" 

trigger OnRun(); 
begin 
InFileName := 'c:\share\Pricing.xml'; 
UploadIntoStream('', '', '', InFileName, InFileStream); 
PricingXML.SetSource(InFileStream); 
PricingXML.Import(); 
Message('Bing!'); 
end; 
 
var 
PricingXML: XmlPort "Temp Pricing Import"; 
InFileName: Text; 
InFileStream: InStream; 
}

Karen W adds: “Newer releases of Lanham EDI use this. I will not profess to the details, but if you want to see additional examples, you can take a look at their stuff.”

Cumulative Updates for Dynamics NAV: February 2019

Pavithra keeps us apprised of the latest CU’s.

Below are the links for downloading Cumulative Update for the Month of February 2019

If you are interested in NAV 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: 
Read ArcherPoint's Blog Follow us on Twitter Follow us on Facebook Follow us on LinkedIn Link to our RSS feed Watch us on YouTube
Get Help Now