That's just part of the version tag that Navision uses. Here's how I make sense of it (and that does NOT mean it's the official explanation ):
NAV = Navision
W1 = World Wide
3.00 = version 3.00 (as opposed to 2.50, 3.70, etc.)
03 = critical update/improvementnumber 03
The Version List field in the table contains individual Version Tags separated by commas. When you import objects from text or a fob file, this field is used by the Import Worksheet to determine whether the imported object conflicts with the existing object in the database. If the object conflicts then the developer will need to resolve that conflict prior to completing the import of the object. The table below describes the meaning of an individual version tag.
Current Meaning of Version Tag: NAVNA3.60.01.43 – Product
NAVNA3.60.01.43 – Region or Country
NAVNA3.60.01.43 – Major Release
NAVNA3. 60. 01.43 – Minor Release
NAVNA3.60. 01. 43 – Service Pack
NAVNA3.60.01. 43 – Improvement or Hotfix
The individual who modifies an object is responsible for correctly updating the Version List with an appropriate version tag(s).
If you examine the Version List of the Country (9) table in Navision 3.70 in the Object Designer, you will see that the version tag is NAVW13.10,NAVUS3.10.01.
This indicates that the object was last modified in the W1 version of 3.10. Additionally, we can tell that it was also modified by the North American Development team in Service Pack 3.10A and no changes have been made to the object since that time.
If, for example, a Partner named Contoso created custom functionality that they sell to all their clients and have further customized the Sales Header table for their customer Northwind, then the Version List for the Sales Header(36) table might look like NAVW13.70,NAVUS3.70.00.44,CONT07.01,NOR01
This would indicate that Contoso had applied version 7.01 of their custom solution to the object released in Improvement 44 and had further customized the object for Northwind. If the partner decided that a subsequently released Improvement with a version number of NAVW13.70,NAVUS3.70.00.51 needed to be imported into the database, the Import Worksheet would show a warning(conflict) and a developer would need to incorporate the changes made in the new Improvement and modify the Version Tags appropriately.
Comments
NAV = Navision
W1 = World Wide
3.00 = version 3.00 (as opposed to 2.50, 3.70, etc.)
03 = critical update/improvementnumber 03
RIS Plus, LLC
The Version List field in the table contains individual Version Tags separated by commas. When you import objects from text or a fob file, this field is used by the Import Worksheet to determine whether the imported object conflicts with the existing object in the database. If the object conflicts then the developer will need to resolve that conflict prior to completing the import of the object. The table below describes the meaning of an individual version tag.
Current Meaning of Version Tag:
NAVNA3.60.01.43 – Product
NAVNA3.60.01.43 – Region or Country
NAVNA3.60.01.43 – Major Release
NAVNA3. 60. 01.43 – Minor Release
NAVNA3.60. 01. 43 – Service Pack
NAVNA3.60.01. 43 – Improvement or Hotfix
The individual who modifies an object is responsible for correctly updating the Version List with an appropriate version tag(s).
If you examine the Version List of the Country (9) table in Navision 3.70 in the Object Designer, you will see that the version tag is NAVW13.10,NAVUS3.10.01.
This indicates that the object was last modified in the W1 version of 3.10. Additionally, we can tell that it was also modified by the North American Development team in Service Pack 3.10A and no changes have been made to the object since that time.
If, for example, a Partner named Contoso created custom functionality that they sell to all their clients and have further customized the Sales Header table for their customer Northwind, then the Version List for the Sales Header(36) table might look like NAVW13.70,NAVUS3.70.00.44,CONT07.01,NOR01
This would indicate that Contoso had applied version 7.01 of their custom solution to the object released in Improvement 44 and had further customized the object for Northwind. If the partner decided that a subsequently released Improvement with a version number of NAVW13.70,NAVUS3.70.00.51 needed to be imported into the database, the Import Worksheet would show a warning(conflict) and a developer would need to incorporate the changes made in the new Improvement and modify the Version Tags appropriately.
WOW Denster 994 - I've fallen way behind 8)
http://www.BiloBeauty.com
http://www.autismspeaks.org