Technology

Architectures: Good, Bad and Ugly

  • Reading time:6 mins read

Four months ago I attended a conference, where I had a chance to listen to Miha Kralj, an architect at Microsoft, talk about architectures. It was one of the best presentations I ever attended, and ever since I had this topic in queue, but never really had chance to write about it. Most of the stuff he talked about reminded me of some bad experiences about architectures on projects I’ve worked on. Most of stuff here is also not my original contribution to the universal pool of knowledge, and I reuse it with the permission of the author, so Miha, thanks! What I did, however, is that I applied general principles to specific Microsoft Dynamics NAV situations.

Continue ReadingArchitectures: Good, Bad and Ugly

Cut the (s)crap

  • Reading time:10 mins read

[I had to edit this post on April 01, 2008. And no, it’s not April Fool’s Prank] 

Have you ever wondered how manufacturing scrap works? Or what it really is? It’s an interesting topic, and yet a very confusing one. It has caused so many headaches to the project team I worked on recently, because nobody really understood it. So, what is manufacturing scrap?

Continue ReadingCut the (s)crap

Why are “mandatory” fields baaad?

  • Reading time:9 mins read

Last time, I gave you a recipe on how to do a bad thing. If you really need to do something bad, I figure it’s better to do it the way that would hurt the least, or the way that isn’t so bad after all. I wouldn’t have dreamt of a comment on that blog post, but Ian came, and gave the perfect example which really explains why things like that *ARE* bad. Funny thing is, how many customers really go for such a requirement, and even funnier, how many consultancies give in. I gave in once, most of you probably did. But, why are mandatory fields so bad after all?

Continue ReadingWhy are “mandatory” fields baaad?

Master data completeness validation

  • Reading time:4 mins read

Microsoft Dynamics NAV has a very consistent user interface, that helps user get used to it pretty fast. Yet it has its own ways, that aren’t so intuitive to most of typical business application users. There is one specific feature which causes a lot of confusion, especially with those users only starting to use NAV. It’s the data persistence: as soon as you enter something in a form, it is automatically saved, you don’t need to press any Save button. Nor is there any Cancel button to forget the changes entered.

Continue ReadingMaster data completeness validation

Accounting vs. ERP: The saga continues

  • Reading time:7 mins read

Running a business using only accounting data can be pretty much the same as driving a car using rear-view mirror only. The purpose of accounting is to provide accurate and reliable overview of financial situation to interested parties. What this financial overview consists of is the stuff that has happened in the past, in other words: history. However, there are many drivers of business success other than just history of events that contributed to wherever you are at the moment.

Continue ReadingAccounting vs. ERP: The saga continues

Accounting vs. ERP: Sticks and carrots

  • Reading time:8 mins read

When referring to their ERP systems, it is pretty common that customers refer to it as accounting software. While it is true that every ERP system embeds some accounting functionality, there is a major difference between these two categories of software. It starts with two things: what computers are good at, and the goal of accounting as a discipline.

Continue ReadingAccounting vs. ERP: Sticks and carrots

Automated version management? Of course!

  • Reading time:5 mins read

Imagine that whenever you edit an object in C/SIDE Object Designer, and save it, the system automatically saves it in the version history. Imagine that it never simply overwrites your previous version, but keeps all of them there for you. Imagine that you can see all of the modified versions of any object, then make any version the current version by doing as much as a single mouse-click, no tedious imports and exports needed. Imagine that this is true for all of the developers on your team. Imagine that it is completely, fully automated.

Continue ReadingAutomated version management? Of course!

Native vs. SQL: The Delta

  • Reading time:9 mins read

Early versions of SQL Server option for Microsoft Dynamics NAV (then called Navision) didn’t scale up as high as one would expect. Although SQL Server itself could scale up to thousands and tens of thousands of concurrent users, running a production environment of an ERP system is way different from running generic lab tests.

SQL Server 2000 brought many improvements, and finally outperformed Navision Database Server at any level of user concurrency. SQL was gaining momentum, and became the platform of choice for new implementations of Navision. When SQL Server 2005 came out, and when support for it was included in Microsoft Dynamics NAV 4.0, it could outperform the native database platform as much as 35%.

Continue ReadingNative vs. SQL: The Delta

Native vs. SQL: The Evolution

  • Reading time:5 mins read

One of the choices a customer interested in Microsoft Dynamics NAV must definitely make is the choice of the database platform. With NAV, there are two possible options: so called native database server, which is not really officially called that (the official name is Microsoft Dynamics™ NAV Database Server), and Microsoft SQL Server.

Continue ReadingNative vs. SQL: The Evolution

Code of coding 4: Die, hard(coding) 2

  • Reading time:6 mins read

In Croatia, most of roads resemble battlefields. They are so full of holes and patches from all kinds of repairs over time, that they have to re-pave them every five years or so. It is an awful waste of taxpayer’s money, and makes you wish for the world of Jennifer Government to come be. Anyway, as soon as they re-pave the roads, not a week usually passes before they come again, with jackhammers and heavy machinery of all sorts, and start drilling away, blocking the road in process and causing mass-frustration, just because some wacko has suddenly remembered that it would be nice idea to pass the optic cable underneath, or some valve started leaking.

Continue ReadingCode of coding 4: Die, hard(coding) 2