Dynamics NAV
-
Why are “mandatory” fields baaad?
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…
-
Master data completeness validation
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…
-
Accounting vs. ERP: The saga continues
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…
-
Accounting vs. ERP: Sticks and carrots
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…
-
Automated version management? Of course!
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…
-
Native vs. SQL: The Delta
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…
-
Native vs. SQL: The Evolution
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…
-
Code of coding 4: Die, hard(coding) 2
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…
-
Code of coding 3: Die, hard(coding)!
Development is an important phase of implementation of a highly-customizable ERP system, such as Microsoft Dynamics NAV, and that’s why I put a lot of emphasis…
-
Version management
When I posted my last relevant post on this blog, I’ve got a comment from infonote (a visitor) how bad it was that Microsoft Dynamics NAV can’t use a…