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.

Installing NAV 2009

• The Role Tailored client and Classic client can be installed on a different computer from where you install Microsoft Dynamics NAV Server.
• To install the Role Tailored Client and the Classic Client, run the Setup.exe.
• After accepting the license, two options will be available. one is Installing Demo NAV and choosing a installation option.
• Installing Demo will install Role Tailored client, Classic Client for SQL and Classic Client for Native database.
• Functionality for the Classic Client for SQL and Native Database remains same like the previous versions, Where as Role Tailored Client option is quite different and new in NAV 2009.

Things I learned in NAV 2009

· Architecture changes that includes Role Tailored client. Classic client still remains with two tier architecture, where as the new Role Tailored Client support three-tire model with Role Tailored Client, Microsoft Dynamics NAV Server which executes business logic and SQL Server.
· The Role Tailored client provides a single document interface (SDI) environment,
· Microsoft Dynamics NAV Server: The new Microsoft Dynamics NAV Server is a .NET-based Windows Service application that works exclusively on SQL Server. It uses the Windows Communication Framework as the communication protocol for Role Tailored clients and Internet Information Services for Web services that access it.
· Microsoft Dynamics NAV Server provides an additional layer of security between the clients and the database. It leverages the authentication features of the Windows Communications Framework to provide another layer of user authentication and uses impersonation to ensure that business logic is executed in a process that has been instantiated by the user who submitted the request.
· Microsoft Dynamics NAV Web services can be used by customers and partners who want to use business logic or use a standard interface to access data from outside Microsoft Dynamics NAV.
· To allow you to write code that targets either the Classic client or the RoleTailored client, a new system property called ISSERVICETIER has been created. If code is being executed on the service, then it returns TRUE. Otherwise, it returns FALSE. You can then use ISSERVICETIER to write code that is explicit about whether it is run on the service.
· When you design a report for the Classic client, you design the layout in Section Designer. When you design a report for the Role Tailored client, you design the layout in an RDL editor, such as Visual Studio Report Editor.
· NAV 2009 has an option to import/export the objects in .XML format also.
· Pages contain fewer triggers than forms for two reasons: The RoleTailored Client has enhanced behavior that is implemented directly into the controls that run on it. Some code previously necessary is now obsolete. Pages are designed to optimize performance, which reduces requirements for existing form triggers.

. Field Groups: Field Groups is a new concept introduced in a table description. When a field displayed in a page in the RoleTailored Client has a relation with another table, the DropDown button displays several default fields from that table. These default fields are set from the Field Groups window, accessed from the table designer. To view the Fields Groups of a particular table:
In the Object Designer's Table list:
1. Select any table and then click Design.
2. Click View > Field Groups. The Field Groups window of that table
opens.

. Using Administration-->RoleTailored Client-->Profile, we can change the default role center for the user.