Best practices
-
Transaction Integrity with Connected Systems
With .NET Interoperability around, it’s very likely you’ll be synchronously calling external web services from C/AL, to exchange data. I won’t go into…
-
SQL Server Configuration Recommendations for Microsoft Dynamics NAV
Microsoft Dynamics NAV Team Blog has just published a mega-useful post about recommendations for configuring Microsoft SQL Server for optimum Microsoft…
-
10 reasons that make design absolutely necessary
Design is one of a kind. Other phases in Sure Step are understood and accepted as good and necessary. But design, do we really do that? Is it really necessary?…
-
Setup-dependent requirements
While designing a custom functionality for a customer, there was an issue with posting groups: the way the custom functionality was designed would result in…
-
Development best practices – the aftermath
So I would guess that was it. I’m just returning to Kristiansand, my Norwegian base, after delivering the “Microsoft Dynamics NAV 2009 Development Best…
-
Development Best Practices
“Best practices” is one of those beloved and hated concepts. There are people who just embrace “best” practices for the sake of their bestness. And there are…
-
5th rule of agile ERP: interface where possible
One of the biggest absurdities about ERP systems springs from the very word we use so often when describing ERP: integrated. ERP is an integrated system: it…
-
4th rule of agile ERP: avoid heavy customizations
You can’t avoid customizations. Vanilla ERP is a great first step, and a valuable tool for establishing common language between the customer and the…
-
3rd rule of agile ERP: focus on value
– “We need a report which groups our sales by product components.” – “And we need it broken down by cost centers.” – “And it must show comparison with last…
-
2nd rule of agile ERP: deploy gradually
How do you eat an elephant? One bite at a time. Swallowing it all at once might be tempting as it has all the potential you need to get into the next edition…