ZUP files in NAV 2009

In the previous versions of Navision, all the user changes and settings will be stored in the .zup file(i.e. Recentely opened databases,etc...) and the user menu level table (i.e Shortcuts,etc...). This functionality has been changed for the RTC in NAV 2009.

There are new tables in NAV 2009, some of them are used to store user settings in RTC. Classic client user changes will be still stored in fin.zup file and user menu level table.

2000000071 Object Metadata

2000000072 Profile

2000000073 User Personalization

2000000074 Profile Metadata

2000000075 User Metadata

2000000076 Web Service

2000000078 Chart

As of my knowledge NAV 2009 RTC user changes/settings will be stored like below:

PersonalizationStore.xml: This file is located at \Administrator\Application Data\Microsoft\Microsoft Dynamics NAV.This file is used to store all user changes like resizing the columns in the pages. You can delete this file, If you want to roll back all the changes.

System will again create this file once you login and logout from the RTC.

Classic client user changes will be still stored in .zup file.

ClientUserSettings.config: This file is located at \Local Settings\Application Data\Microsoft\Microsoft Dynamics NAV.This file is created by installation setup, while installing RTC Client and this holds the parameters useful to call the Microsoft NAV Server. This file holds NAVServer, Instance name, NAV Server port. Once user click the Role Tailored Client to open, process will call the above file.

CustomSettings.config: This file is located at Program Files\Microsoft Dynamics NAV\60\Service.

I guess this file is called by the Microsoft NAV Server to connect the SQL Server, related database and holds other important parameters.

2000000071 Object Metadata: As the name specify (i.e. Metadata : Data about Data) this table holds data about all the objects in the database. Data into this table will be inserted while compiling the object.

2000000072 Profile: It is the customization of the user interface (Role Center) for the end-user to match a specific role. Profiles can be accessed from Administration-->Application Setup-->RoleTailored Client. This is the default setup for all users and we can customize the setup for the user using User Personalization.

2000000073 User Personalization: User Personalization is used to assign a configured profile to a user. User Personalization can be accessed from Administration-->Application Setup-->RoleTailored Client.

2000000074 Profile Metadata: This used to store the custom chages done to the profiles.We can delete all configuration changes made for the profiles from Profile Card--> Fuctions-->Clear Configured Pages.

2000000075 User Metadata: In the RTC, if user customize any pages or navigation panes a record will be inserted into this table. This used to store all custom changes done by the user to the pages in the RTC. We can delete all personalization change made by the user from User Personalization Card--> Fuctions-->Clear Personalized Pages.

2000000076 Web Service: I will study this functionality and update soon.

2000000078 Chart: I will study this functionality and update soon.

Implementing Microsoft Dynamics NAV 2009

Microsoft Dynamics NAV 2009 is the latest release of the NAV application (formerly known as Navision) from the Microsoft Dynamics family of products that brings a 3-tiered architecture, web services enablement, and many more exciting features, to the well established Enterprise Resource Planning (ERP) solution. Here is the first book to show you how to implement Microsoft Dynamics NAV 2009 in your business and this book authors are David Roys,Vjekoslav Babić.

Implementing Microsoft Dynamics NAV 2009

Calculate Inventory Exceptions

Calculate Inventory Batch in the Phys. Inventory Journal will process the items based on the filters given and inserts items in the physical inventory journal. In the physical inventory journal Qty. (Calculated) field value will be calculated from the item ledger entry table and Qty. (Phys. Inventory) field value will be calculated from the warehouse entries if the database is using warehouse management.

Calculate inventory report has two exceptional cases:

Case I: If the Item has Warehouse Entries and doesn't have single Item Ledger Entry then "Calculate Inventory" function in Phys. Invt. Journal will not create adjustment line.

Case II: (For Same UOM) Item's Qty. (Base) differs from Quantity in Warehouse Entries.

"Calculate Inventory" function in Phys. Invt. Journal is creating two adjustment lines with incorrect Quantity for the same item instead of creating one line.

Change Log Entry for the Object table

Microsoft Dynamics Navision has below kind of object types:
Table, Form, Report, Data port, XMLport, Code unit and Menu suite.
Other than the above object types, there are other object types which are hidden and useful for data management.
i.e. Table Data, System, Field Number
Object (2000000001) table holds data for all the above object types.




When a table object (i.e. .fob file) is imported into the database, two records will be inserted into the Object table (2000000001).
1. First record with Type value 0 (i.e. for Table Data). This is useful to manage data in the specific company.
2. Second record with Type value 1 (i.e. for Table). This table object is unique for all companies in the database.

Because of this change log entry table holds two records with “Type of Change” Insertion, one with "Primary Key Field 1 Value” 0 and second record with "Primary Key Field 1 Value" 1.

This only applies to the table object and for the other objects like forms, reports and etc, only one record will be inserted into the object table and change log entry table.

Top 5 qualities of a great Microsoft Dynamics consultant

Top 5 qualities of a great Microsoft Dynamics consultant:

• Industry expertise
• Application knowledge
• Creativity
• Patience
• Communication

Click this to read this excellent post from Vjeko.

Report Designing in NAV 2009

• In NAV 2009, if a report consists of two indented data items, instead of running a nested loop, the records are returned in a flattened state, which means, both data items, the parent and the child are joined, and returned together.
• There are two new components in the report objects, they are as follows:
  • Request Page
  • Report Definition Language (RDL) data
• Report chagnes takes advantage of on SQL Reporting Services technology. i.e.
  • Visual effects with charts and graphical representation.
  • Richer aggregates, not only SUM but also AVG, MIN, MAX and more.
  • The possibility to create interactive reports (interactive sorting, hide/collapse item).
  • Out-of-the box export possibility to Excel and PDF for all reports.

Pages in NAV 2009

• Pages in NAV 2009 has distinct properties that are not available in forms PageType, CardFormID, InstructionalTEXTML, LinksAllowed.
• In NAV 2009 field's visibility can be controlled by assigning an expression that returns TRUE or FALSE to its visible property instead of Yes or No.
• Fileds in the pages have an extra property called ExtendedDataType. The options available are as follows:
  • None
  • Phone No.
  • Url
  • E-mail
  • Ratio
• Every page must have a container which is the top most element of the page.
• Importance property of the filed in the pages is useful to show the data in this field without cramping all the information together.
• New Pages can de deployed into the RoleTailored Client by adding the pages into the related Role Center page object.