June 9, 2017
ArcherPoint Dynamics Developer Digest - vol 143
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.
Modifying the MenuSuite in Dynamics NAVMichael H. shares his opinion that we (Dynamics NAV partners) should be customizing Dept. - Partner MenuSuite 1080, not Dept. - Customer MenuSuite 1090. He contends that 1090 is for the customers to customize themselves. Matt T. confirms, “Not an opinion, that's just flat out the way it is supposed to be done. Modify the partner MenuSuite, compile all of the MenuSuites, done.”
NAVUG Focus – Learning In-DepthJon Long shared that “NAVUG Focus was quite exciting. Matt and I presented sessions on Upgrades, Auto Testing, and the future of .NET. These are difficult subjects, but, very enlightening. Great question and answer sessions in every session.” He adds, “It was really great to meet all the ambitious customers.”
Visual Studio Code is now the "Official" PowerShell EditorBill W. shares this tip with us, stating that VS code is now the “official” PowerShell editor, and it is also the future home of Dynamics NAV development. According to Bill, “You might as well install Visual Studio Code now.” He also shares an older, but still a good breakdown, of the PowerShell
Leadership LinesPandiyan shares a familiar corporate story… Every day, a small ant arrives at work very early and starts work immediately. She produces a lot and she is happy. The chief, a tiger was surprised to see that the ant was working without supervision. He thought if the ant can produce so much without supervision, wouldn’t the ant produce even more if she had a supervisor? So he recruited a bee who had extensive experience as supervisor and who was famous for writing excellent reports. The bee’s first decision was to set up a clocking in attendance system. The bee also needed a secretary to help write and type reports, the bee recruited a rabbit, who managed the archives and monitored all phone calls. The tiger was delighted with the bee's reports and asked her to produce graphs to describe production rates and to analyze trends, so that he could use them for presentations at board meetings. So, the bee had to buy a new computer and a laser printer and recruited a cat to manage the IT department. The ant, who had once been so productive and relaxed, hated this new plethora of paperwork and meetings, which used up most of her time. The tiger concluded that it was high time to nominate a person in charge of the department where the ant worked. The position was given to the monkey, whose first decision was to buy an air conditioner and an ergonomic chair for his office. The new person in charge, the monkey, also needed a computer and a personal assistant, who he brought from his previous department, to help him prepare a work and 'Budget Control Strategic Optimization Plan.’ The department where the ant works is now a sad place, where nobody laughs anymore and everybody has become upset. It was at that time that the bee convinced the boss, the Tiger, of the absolute necessity to start a climatic study of the environment. Having reviewed the charges for running the ant’s department, the Tiger found out that the production was much less than before. So, he recruited the owl, a prestigious and renowned consultant to carry out an audit and suggest solutions. The owl spent three months in the department and came up with an enormous report, in several volumes, that concluded...the department is overstaffed. And, who does the tiger fire? Of course, the ant,” because she showed lack of motivation and had a negative attitude.” The moral of the story: Always understand who you are and where you are. Rise and shine, keep working without seeing whether you are monitored or not. Stay abreast of what is new in the Microsoft Dynamics NAV community and at ArcherPoint by subscribing to our monthly newsletter, Better Business, by completing the form in our Resource Center. And, if you are interested in NAV development, be sure to see our collection of NAV Development Blogs.
- 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