Microsoft Dynamics NAV 2009 Upgrades and the RTC Reporting Nightmare – Erik P. Ernst about Navision and the Dynamics Community – Dynamics User Group

Typically I’m not the one who is writing too much about “technical issues” in my blog. But that doesn’t mean that I’m never dealing with “technical issues” – in fact programming and other technical issues is what I’m doing more than 50% of daily working time. And while this blog post is more “technical” than normally, then it’s not really technical. It’s more about my experiences with NAV 2009 upgrades as seen on a little higher level.

Until recently then I have not been doing so much work on NAV 2009. Most of my client as a freelancer have older versions, and are very happy about it. But now I have just finished my first full Dynamics NAV 2009 upgrade. Before I have done one other NAV 2009, but to a client who didn’t want to use the RoleTailored Client. And right now I’m doing my second RTC upgrade. Not much for many of you, but surely enough to get the feeling of what this “NAV 2009” is all about!

On the surface, then a NAV 2009 upgrade isn’t that much different from any other Navision upgrade. And over the 20 years where I have been working with Navision then I surely have done my share of the upgrades. And until NAV 2009, then it has always been almost like riding a bicycle. Once you have learned, then you will always have it.

Upgrading Pages

For Dynamics NAV 2009 then it was going great with the tables, forms, codeunits etc. All the object types that didn’t change too much from the previous versions. And when it came to the forms, then in both of the projects, I actually decided to create the new pages again using the page designer, instead of actually using the Page Transformation Tools. I did this basically because I’m a bit lazy of nature, and I estimated that it would take me much more time to setup and define the files for the Page Transformation Tool, than to manually upgrade the changed forms and to recreate the 10 new forms that the customer had in his database.

So I can’t even say how much it takes to use the Transformation Tools. At least there is a lot of documentation available regarding page transformation, so I am actually felt quite comfortable that it would not had been a problem, in case the client would have had a lot of new forms. But it is my own estimate that it would require at least 30-50 new forms, before it would be worth to start using the page transformation tool.

Upgrading Reports

When it came to upgrading reports, then it was a much more troublesome. I actually never found any way to upgrade the RoleTailored Part of the reports. Yes, there sure is a function to “Create Layout Suggestion”. But if what you really just wanted to was to insert a few new fields in the standard NAV report, then this function should really not be used. The function deletes the existing layout, which in most cases means that all the optimization and layout improvements done manually by Microsoft will disappear.

Additionally most standard reports are loaded with small controls which are hidden when printed with the Classic Client, but used when printed in the RTC. That makes editing the reports even more difficult.

So my conclusion to this was that it was much easier to upgrade all the reports manually! Both in the Classic and in the RTC.

Upgrading documents like Invoices and Order Confirmations was an bigger task. I think I was reading somewhere on the internet, that one should estimate 8-16 hours on upgrading just one document. I was really laughing about that, until I was sitting there and doing it myself. The first Invoice took me almost 20 hours!!! And it wasn’t because Visual Studio was all new for me, as I have been using Visual Studio to maintain this website for years! My next document (a Order Confirmation with an almost identical header) took me almost 10 hours and the additional document reports all took between 6-10 hours.

via Microsoft Dynamics NAV 2009 Upgrades and the RTC Reporting Nightmare – Erik P. Ernst about Navision and the Dynamics Community – Dynamics User Group.

How to apply the 6.0 Hotfix to the existing Demo Install

Usage Scenarios

4.1 You have downloaded the RTM image of Microsoft Dynamics NAV 2009 and want to update it with the Hotfix.

  1. Download the HF package from PartnerSource.
  2. Copy the updated database files into the existing database folders and overwrite the existing databases: Demo Database NAV (6-0)_Data.MDF, database.fdb, and database.fbk.
  3. Overwrite the existing form transformation tool files in the Transformation Tool folder with the updated form transformation tool files.

4.2 You have installed the demo database and want to update it with the Hotfix.

  1. Download the HF package from PartnerSource.
  2. Detach or delete the existing Demo Database NAV (6-0)_Data.MDF.
  3. Attach the updated Demo Database NAV (6-0)_Data.MDF from the HF package as described in the C/SIDE online help. To view the online help, on the Open Database form, click Help. In the Microsoft Dynamics NAV Classic Client Help, in the Open Database topic, click the Microsoft SQL Server Option for Microsoft Dynamics NAV link and then go to step 8.
  4. Overwrite the existing form transformation tool files in the Transformation Tool folder with the updated form transformation tool files.

4.3 You have downloaded the RTM image of Microsoft Dynamics NAV 2009 and want to update it with the Hotfix, and you have already started transforming custom forms to pages.

  1. Export language modules for all pages.
  2. Export forms.
  3. Retransform the forms, including report request forms, in your development database to pages by using the new form transformation tool.
  4. Import pages.
  5. Import language modules for pages.
  6. Retransform the forms in your development database to pages by using the new form transformation tool.
  7. Import the transformed pages and report request pages.
  8. Import the language module into the development database.

List-page to Card-page relationship

To successfully create a logical relationship between a List page and Card page in RTC, perform the following steps:

  1. In Dynamics NAV classic client, go Tools || Object Designer || Page.
  2. Select the List page required || Click Design || Go to first blank line preceding the Field Controls
  3. Select the page properties (Shift+F4) || Page Properties Window Displays.
  4. In the Page Properties Window:
    1. Change the Value of Editable to NO.
    2. Change the Value of CardFormID to the Card Page required (Enter the object ID).
  5. Save and Compile the List Page.
  6. Test the List page :
    1. In Dynamics NAV 2009 SP1 –>> Select and Run the Object Designer :
      1. Double Click a Record, the Card Page for the Record Displays.
    2. Alternatively, In Dynamics NAV 2009 –>>  At Run cammand, type : DynamicsNAV:////runpage?page=<page ID> to invoke the Listpage
  7. The above simulates the logical relationship between Customer List and Customer Card in RTC.

SQL Attachments – Access to object tracking table denied

The Classic client allows attaching a SQL Server database from an .mdf file. When a database is attached this way, permissions to the object tracking table are not set correctly. The user under which the Microsoft Dynamics NAV Server service is executed needs permissions to this table. The service stops responding when you try to start the RoleTailored client, and the event log reports that access to the object tracking table was denied.

Resolution – Workaround

  1. Stop the Microsoft Dynamics NAV Server service.
  2. Stop the SQL Server service.
  3. Open a command prompt.
  4. At the command prompt, type the following command:
    Sqlcmd -d “Demo Database NAV (6-0)” -q “GRANT SELECT ON [dbo].[Object Tracking] TO [NT AUTHORITY\NETWORK SERVICE]”
  5. Start the SQL Server service.
  6. Start the Microsoft Dynamics NAV Server service.