ArcherPoint Dynamics NAV Developer Digest - vol 281
The Dynamics NAV and Business Central 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/BC experts and devotees around the world. We hope these insights will benefit you, too.
RDL Report Writer Tip
Kyle shares his Developer Tip of the Day: “In AL, if you have an RDL report layout open in Report Writer, you don’t have to keep launching and closing the report builder to make your changes take effect. Just Save the RDL – remember that everything in the AL world is just a text file. As soon as you have saved, you can publish to your Docker container from VSC.”
Edited to note: “I should qualify this advice. This works as long as you are working exclusively on the layout. If you make AL changes that would impact the dataset, you need to exit out of Report Builder and launch it again from VSC.”
Page Extension – Don’t Do This
Bill W offers advice: “Don’t do this. I’m guessing this creates some kind of infinite loop during compile, and if you don’t realize you did it, it’s somewhat difficult to track down.”
pageextension 60024 “Some Page Ext.” extends “Some Page”
{
Layout
{ addafter(“Pick-up”)
{ group(“Pick-up”)
{
Kyle notes: “I didn’t think you could reference your own page extension. Did that pass a regular compile?”
Bill W responds: “No, it doesn’t compile. It would start and then I’d see Microsoft.Dynamics.Nav.EditorServices.exe CPU spike, and it would never complete. I had my container also go down in the middle of the process, so I was run off the trail of it being a problem with the code a couple times. In the end, by switching back and forth between the last working commit, I was able to narrow down the code that caused the issue.”
Kyle suggests: “Sounds like something you should report to github.”
Report Not Picking Up New Records
Tim L shares his issue: “I’ve run into a situation where records are being injected into a staging table, but the processing report isn’t always picking up the new records. Has anyone run into this? NAV2015, SQL Server 2012.”
Kyle offers: “SELECTLATESTVERSION”
Tim replies: “This might be perfect. It seems to explain what I’ve been seeing.”
Business Central 15: Quantity Calculated in the Physical Inventory List
Len shares this tidbit: “In BC15, I just found out the stock Phys. Inventory List (the report run from the Phys. Inventory Journal) shows the Qty. Calculated, but it actually rounds to the nearest whole number. The report format for that field is #,##0, which will not show any decimals. You can simply update this using Custom Report Layouts, but I found it interesting!”
Performance Tuning Guide for Business Central
Saurav shares: “The Microsoft Dynamics 365 Business Central performance team has just published a new performance tuning guide for Business Central on premises and online.”
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.