ArcherPoint Dynamics NAV Developer Digest - vol 227
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.
An Important Safety Tip When Publishing an AL ExtensionKyle warns: “Important safety tip: if you are publishing an AL extension, do not accidentally change the ID field in app.json. The resulting database will register your extension twice, under the same name but with two different IDs.” Bill W agrees: “The AL: Go! in VS Code will generate a new one. Also, if you fork or copy a project change the ID with a new GUID. I use this Insert GUID app from the VS Marketplace.
You Picked the Right CareerU.S. News and World Report recently released their best job rankings for 2019, and software developer is at the top of the list. Seven factors are taken into account for the top 10 job rankings, including median salary, employment rate, and stress level. Learn more about how they rank the best jobs and view the best 100 jobs in America.
Recurring Job Queue IssueAdrian asks the team: “A client has a recurring job queue entry that runs every 10 minutes. The status of the job queue entry is frozen as Finished about every 10 days or so. I checked the setup, but everything looks good to me. What could be the reasons causing this and how can we fix it? Thanks!” Kyle wants to know: “Is the JQE running custom code? Is this new code? Or did it work for a while for weeks and weeks and then recently start hanging?” Tim adds: “And sounds like no errors in the log...” Adrian confirms: “Yup, it is running a custom code. I am not sure whether it is a recent issue. I will need to check with the client. Nope, no errors in log.” Michael H suggests: “Check cumulative updates.” Kyle offers: “Let us know when you find out when the problem started and whether that coincides with a recent code change or addition. If you want to DM me a text export of whatever the JQE is running, I'm happy to take a look to see if I notice anything or have any ideas...”
Adrian includes: “The client said the issue has occurred since NAV 2016 was installed”, then adds, “The client decided not to proceed any further to debug the issue. But I still wanted to say thank you for all of you guys' input!”If you are interested in NAV development, be sure to see our collection of NAV Development Blogs. Read the "How To" blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central, and contact ArcherPoint if you need assistance with Dynamics NAV or Business Central.
- Login Error: Communication protocol mismatch between client and server
- Creating a Date Table in Power BI
- How to Make Measures Total Correctly in Power BI Tables
- The Microsoft Technology Stack – What It Is and Why You Should Care
- The Top Eight KPIs Retailers Should Be Tracking (with Formulas) for Your Retail KPI Dashboard