Skip to content

ArcherPoint Weekly Microsoft Dynamics NAV Developer Digest – vol 1

The ArcherPoint technical staff—made up of developers, project managers, and consultants—is constantly communicating internally, with the goal of sharing helpful information with one another.

ArcherPoint’s technical staff pose questions, find answers, and share new discorveries about Microsoft Dynamics NAVAs they run into issues and questions, find the answers, and make new discoveries, they post them companywide on Yammer for everyone’s 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 group—so we thought, wouldn’t it be great to share them with the rest of the Microsoft Dynamics NAV Community? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Beginning with this blog, we will present each week a  collection of thoughts and findings from the ArcherPoint staff. We hope these insights will benefit you, too.

Read all our ArcherPoint Developer Digest blogs.

Kyle Harding on SQL database settings:

Developers beware: When you are restoring a SQL database during a go-live, always be sure to set the Recovery Model to Full. I just found a customer's production database with the recovery model set to Simple, and that means the transaction log backups had been failing for a very long time.

Cory Power on installing demonstration and developer versions of Dynamics NAV:

Never do a "Demo" install unless you do not care about previous versions of NAV 2009 and up. The preferred install method is to use the "Customize" link under the "Developer" install. This will allow you to choose the install folder path, Dynamics NAV instance name, SQL instance, database name, and ports.

Faithie Robertson on table changes in Dynamics NAV 2013 R2:

The attached is a must read for developers on Dynamics NAV 2013 R2. There are changes in how we deploy a FOB, in how table changes should be handled when delivered, and even in the creation of the Instance (note "SQL Server Command Timeout” should be set to 10:00:00 - the default is 00:00:30). The bottom of the document has a set of "best practices" for both single and multi-tenant environments. I'm working with Microsoft Support to determine the best way for us to deploy NAV2013 R2 in the three database environment.

Read Faithie’s blog on this subject.

Read the document, The New Table Synchronization paradigm in Microsoft Dynamics NAV 2013 R2, prepared by the Microsoft Dynamics NAV Team.

Also read MSDN's documentation, Understanding and Configuring Session Timeout.

Matt Traxinger on PowerShell:

PowerShell may look like old DOS, but it really is a very, very powerful tool. Want to automatically spin up service tiers when loads get too high? PowerShell can do that. Need to parse a text file and add code for dataport logging? PowerShell can do that. Want to auto-version our objects and enforce release standards? We can do that too. Want to build a version control tool? PowerShell is a great place to start. It's also easy to learn. I went from not knowing how to script anything with it to building a program in a day

Look for more developer insights each week. Have a question you’d like answered? Send it to us. We’d love to hear from you.

Blog Tags: 
Read ArcherPoint's Blog Follow us on Twitter Follow us on Facebook Follow us on LinkedIn Link to our RSS feed Join us on Google+ Watch us on YouTube