October 28, 2016
ArcherPoint Dynamics Developer Digest - vol 116
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.
FOB, TXT, and DELTASaurav Dhyani shares his thoughts on an article written by Vjeko, titled C# Injection: Don’t Trust the FOB. He agrees: FOB, not good. TXT, good. DELTA, best. Others agree and note that we should always recompile everything we import after importing whether FOB, Text, or Delta. Jon Long also notes: “Another, perhaps even more dangerous reason to not trust FOB's, is that a text file can be saved accidentally, or on purpose, with an FOB extension. Obviously, if you were to import this type of "FOB," it would overwrite everything without opening the import worksheet. This could be especially dangerous in a dev environment that has no proper source control. That is why I always open FOB's in a text reader first, to make sure it's actually an FOB. So, yes, I agree, FOB's should not be trusted, but, it's not just because of injections.”
Register as a Microsoft App DeveloperAre you interested in publishing an App to the App Store? You will need to register as an app developer with Microsoft first. A developer account lets you submit apps and add-ins to Microsoft marketplaces, including the Windows Store, Office Store, Azure Marketplace, and more to come. You can sign up for either individual/student account which costs approximately $19 USD, or a company account which costs approximately $99 USD. This is a one-time registration fee and no renewal is required.
Concerns with Microsoft Dynamics NAV ExtensionsWaldo shares his concerns with Dynamics NAV Extensions, part 2 of 3. He shares these common concerns:
- Why can’t I see the code?
- Why is my IP not protected if I share my code?
- Can you use extensions in the wrong way?
- Are extensions a solution for upgrades?
- Why do I have to develop in something other than C/SIDE?
- Will on premise NAV die?
- Will my developers’ knowledge be wasted?
Want to learn more?Have other concerns or questions about Dynamics NAV? Or just want to be in the know about the Microsoft Dynamics NAV community and ArcherPoint? Subscribe to our monthly newsletter, Better Business, by completing the form in our Resource Center and never miss an update. If you are interested in NAV development, check out our collection of Dynamics NAV Development Blogs.
- Login Error: Communication protocol mismatch between client and server
- Creating a Date Table in Power BI
- The Top Eight KPIs Retailers Should Be Tracking (with Formulas) for Your Retail KPI Dashboard
- Difference Between IaaS, PaaS, and SaaS And When You Need to Use Them
- The Microsoft Technology Stack – What It Is and Why You Should Care