Starting with NAV2013, Microsoft increased the size of the “Version List” field after having been hammered for years to increase it but this is not the cause of this topic.
I wanted to check how long the field was (bad memory!) so I checked the NAV virtual Field-table and found something strange (actually 2 things).
First the size was not 250 chars but only 248. Why? I don’t know. Well, 2 chars on 250 won’t make the difference anyway.
BUT what drew my attention was the data type of the field: It wasn’t “Text” like I expected but “OemText”!
I never saw this datatype (ahum … http://dynamicsuser.net/nav/b/mark_brummel/posts/nav-2013-unicode-oemcode-amp-oemtexT … Remember the bad memory!). So I checked if I could create a field in a new table using this datatype but I couldn’t. It didn’t show up in the list.
Good. Why do they use “OemText” and not “Text”. What is the difference. There must be one. So check the table in SSMS to see if it shows up.
What are the differences between a “OemText” and “Text” in SQL Server?
Well, we know that starting with NAV2013, text-fields are Unicode. That means the nvarchar-datatype in SQL.
But “OemText” is NOT using nvarchar but varchar in SQL! So the versionlist is NOT Unicode!
Oh. Also fields “Company Name”,”Name”,”Locked By” in the Object-table are “OemText”.