All around NAV dev and test
Silvester's day is still long and no way to go and read a book in bed. But I will close down my laptop anyway before we prepare for Oudejaaravond, get together with our neighbours and 'hell' brakes lose at midnight ... and all becomes quite on New Years Day.
With the introduction of the Microsoft SQL Server option for NAV the specific way of sorting Code fields (the Navision way) was no longer possible when running NAV on SQL Server. The Dynamics Book wiki gives a good description on the differences not in the least because of the filtering examples.
As Code fields are text fields the basic sorting mode on SQL Server is a text sorting. However to provide some sort of numerical sorting for Code fields the SQL Data Type property was introduced having the following three options:
In all years those I never did get to explore these different options until a couple of weeks ago. For those, like me, who also did not, some examples.
Design: table with one field (PK) Varchar of Data Type Code with SQL Data Type Varchar (default).
Design: table with one field (PK) Integer of Data Type Code with SQL Data Type Integer.
Design: table with one field (PK) Variant of Data Type Code with SQL Data Type Variant.
As I did take my youngest son out sleigh riding (in fact: the whole family), got outside and was marveled about the beauty in (almost) black and white, sat at the fire and pick-up my stamp collection, stayed in bed and read that one book, and played Ticket-to-Ride with my family, there's one thing left to do before the turn of the year: write at least one of these posts that have been hanging in-the-air for sometime.
And I must confess this provided me a very good alibi to get out of bed first before everybody else in the house on Silvester's day; the last to get out has to treat all the others!
Among others, this one: the other day I was involved with this mibuso thread: COA sorting. Although the issue reported was a server issue, David Singleton and I got to talk about the localization to "... allow sorting [...] in line with legal requirements".
This whole localization thing kept on lingering in my mind. The issue was not new to me having been involved with quite a number of localizations. But you might recognize I always get a bit restless in case of useless/redundant efforts. Restless? Useless? How does this relate to COA Sorting you might wonder?
Have a look at this list David composed on GL Account as Text instead of Code. At least 7 countries do have a localization here, where the data type of the PK field of the G/L Account table has been changed form Code 20 to Text 20.
Well, yes, as this pervades a vast amount of objects especially if the local version also includes Cost Accounting. And for what use? Don't get me wrong: this localization was useful and has been so far when running NAV on it's proprietary database server. However, when running on SQL Server, there is no difference between the sorting on Code or Text fields. Or as David puts it: accounting sorting and telephone book sorting.
And now I am getting to my point: with version 7 NAV will only be running on SQL Server so this G/L Account localization will become superfluous. Hope like me MS has thought of that.
OK, this one is not hanging anymore. Finish. Basta. But one other is: did you ever play with the SQL Data Type property?
I guess it will be as white as not many of us around here in NL can remember. Enough snow to take my youngest son out sleigh riding. Enough snow to silence down humdrum noise. Enough snow to go outside and be marveled about the beauty in (almost) black and white. Or to sit inside at the fire and pick-up the stamp collection I started to pick up again - after 30 years! Or maybe write some more posts that have been hanging in-the-air for sometime. Or should I just stay in bed and read that one book I still didn't get to finish? Play Ticket-to-Ride with my family. We're real fanatics, at least we were last year, so let's see if we will get into the same flow.
Curious what you all well be doing the coming days. Whatever it will be: I hope it will be merry and bright. Wherever you are, whatever you believe, whomever you love. Merry and bright, I say.
The version list issue I reported you on yesterday kept on lingering in my mind today thinking this should be fixed by MS and can easily be fixed!
I wrote that ...
... we had various discussion between our GDL team and the build team that any localization of the TIF data should be reflected in the version list of the page. To no avail.
The main reason that it was to no avail had to do with the fact that ...
... the value of the version list of these pages is directly copied form the associated form, which does only contain the w1 part and no local part ...
..., no version info was registered in the TIF data, and pages were created on the fly during the build of a NAV database; i.e. pages were not stored in the NAV's team source control system. Now with the dawning of NAV 7 and the end of the Forms era this whole process has become superfluous and the version list of pages can now be maintained alone.
As I deem this an improvement for development I have posted this as a suggestion on MS Connect.
Do you, like me, want this improvement go to my suggestion on MS Connect and vote on it!