Now that the native database is destined to disappear, it is more than ever time to migrate your database to SQL Server.
And even though I want to push forward to get on with the next test (make it turn GREEN, son), I owe myself, and OK you too, a little bit more explanation to the second part of my previous post. Well, uhhh, actually, I have to confess, Bas, my TDD guru, gave me some small hint on this.
Getting our first two tests, test #1 and test #2, working (GREEN! … GREEN! … GREEN!), we successfully implemented the first part of our feature, i.e. the function CalcDocAmount, leaving us now with it’s counterpart: the verification of the manually entered total amount of the document (invoice).
We already have our first test function PIwithOneLine in codeunit 60000 (Test Doc. Amount) and our second test function will have a lot in common and thus we will create a PIwithTwoLines test function as a copy of PIwithOneLine (you might recall one of my first blog entries on how to copy functions in NAV).
At a client I was trying to start the NAV 2009 R2 Service Tier. The client has a non-english character in the database name and the service tier complained and would not start.
There we go. Let’s turn to our companion on this journey, our Test List, pick out our first test:
QR codes (abbreviated from Quick Response code) are appearing in many different places today, and they are found to be quick and efficient when it comes to working with mobile phones and other devices which can read them. QR Code is a multipurpose instrument and it can hold all sorts of different types of valuable information like your company’s or your salesperson’s contact details, sales invoice information, promotional codes, location information, checksums, amounts, web links etc., which you can read using a QR code reader to automate some of the routine manual processes, like typing in things manually.
Vertalen
