ArcherPoint Microsoft Dynamics NAV Developer Digest - vol 7
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.
As 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. Each week, we present a collection of thoughts and findings from the ArcherPoint staff. We hope these insights will benefit you, too.
Dan Sass shared a story from MiBuSo on Record Link impact on performance:
Saw this on Mibuso and thought it was worth sharing:
The story centers on a NAV 2009 installation that experienced significant slow-down for a particular company.
From the post:
"It turns out the Record Link table was killing us. It needed a compound index which isn't there by default. We have about 4,500 records in this table, mostly for our one 'problem' company (it's a "DataPerCompany=No" table). And, just about every table read automatically checks Record Link so the client can show that little "LINKS" notification in the status bar. So an inefficient index in this single table can affect performance all over the place."
Jon Long in reply to Dan Sass:
2009sp1 also has a bug that creates massive slowness on the Item table if they have more than 10K tables. It has something to do with the blob field for pictures on that table, even if they don't use pictures. I'd be curious if they have more than 10K items in that company. I think MS fixed it in a subsequent 2009sp1 platform build.
Never heard of the Rec. Link table causing performance issues.
Alan Campbell shared this blog about innovative companies and the need for customer feedback (or not):
Why Steve Jobs Didn’t Listen to His Customers
"It's really hard to design products by focus groups. A lot of times, people don't know what they want until you show it to them."—Steve Jobs
Whether or not you agree with Steve Jobs, this is an interesting read about how innovators think.
Dan Sass shared this interview with McKinsey’s Travis Fagan about Understanding the Services Revolution:
Understanding the Services Revolution
The services sector has come to dominate the global economy, yet innovation in that sector has accelerated only in the past decade. This is a fascinating look at how the services industry is changing rapidly.