RTC Client Random Crash - SOLVED!

In my last post RTC - Random Crash I talked about Role Tailored Client random crash on whole system, which could not be explained with any, lets just say, logical explanation. It crashed on all network stations except on Server and with SUPER user.

After cooperation with Microsoft and other consultants, we still didn't find root cause of this problem. Even after applying all newest hotfixes and installing latest build of NAV 2009 everything still crashed.

After a while, whole network crashed. We managed to trace root problem and it led to blade server UTP port. Problem was with UTP cabel which, somehow, got unplugged from port and disrupted ERP data flow. After checking cables and plugging in the cable, as it should have been plugged in, RTC stopped crashing and users were able to work properly.

There is one immediate question: Did classic client work all this time? Answer is: Yes.
As NAV 2009 RTC client requires more bandwidth than classic client, users managed to continue their everday work in classic client.

This goes to show that it isn't always problem with software.

Dynamics NAV 2013 Beta Available!!

Beta version of the new Microsoft Dynamics NAV release is ready for download from Partner source.

There are few localized versions available and the W1. For some time now, teams are working on localizations for other countries, but for test purposes and sneak preview W1 will be just enough. As Vjeko announced on his blog, there are lots and lots of great new features in the new 2013 release! There is a lot to look out for!

Here is one screenshot from new NAV 2013, and even from this picture you can see that new NAV 2013 is something else!

 Also all of you want to get more acquainted with new NAV 2013, there are lots of documentations, system requirements, upgrade guides, what's new,.. available for download from Partner source web site.

RTC Client Random Crash #1

There is something strange going on with new R2 RTC client.

For no reason what so ever, client started crashing on all end-user workstations. What happend? Is it firewall? Is it anti-virus? Is it trojan? We still don't know. Windows event viewer returned values through it's log which we can't interpret as much as we would like to. Can you maybe make something of this:

And is immediately followed by this error:

Possible Workaround , but still…

This error appears on every workstation except super user , and on server. We already tried to set permissions on file system, tried to redefine user roles, but no success. While searching Internet I found that other partners also had this issue. Some workaround can be achieved through compiling User Personalization table. That's right, compiling system table right on the users production server. After compiling this table you will (most likely or 100%) crush Microsoft.Dynamics.Nav.Server.exe. After that you just need to start Dynamics NAV Service and users wil be able to start their RTC clienst.

We are currently in close cooperation with Microsoft trying to resolve this issue with RTC client.

I honestly hope that my next post will be with topic like „SOLVED!“

DynamicsWorld Post

Another article from my blog has been published on MSDynamicsWorld.com: Dynamics NAV article. Many thanks to Jason, for contributing in it's publishing.

Calling Classic Reports From RTC

Starting classic reports from the Microsoft Dynamics NAV role-tailored client (RTC) is a common end-user request. But the design of the RTC client itself didn't provide an easy way of calling these reports via GUI integration with specific business processes of end user. So to deliver on this customer request you have to do a little customization to expose these reports. In this article I'll show two little tricks of how to call classic reports without need of further thinking what data you're actually trying to show.

Dummy Game

The idea behind the "Dummy Game" is a simple trick of setting one dummy data set in as the first record set of a report. Basically this dummy data set will act as the data provider bookmark from the RTC client – or it will copy data from an RTC client row into report field as parameter.

In my example I'll use my custom report "Vendor balance“which will be called directly from the Vendor Card Page. It is basically a report we made for NAV classic reports and put it on the vendor card. The problem with this report was that it was still behaving like a classic NAV report despite advanced functionality of calling it directly from a vendor record. And the user needed to enter vendor data from vendor card from where it was called – a double job. So here's the dummy secret.

In first data set of the report we've placed the Dummy Data item.

The role of this dummy filter was to filter data of page that it was called from and set the filter for the report Record Set data. All of C/AL code is inserted into OnPreReport() trigger.

 

And that did the trick.

But while using this Dummy Game trick we noticed one additional misleading error which could be misleading for end user directing them to enter data into report request form even though it is not needed . All data transferred from RTC on to the classic report with this Dummy Game is not shown in report fields. In this example we transferred Vendor VAT No. And it was not shown on the request form of the report, but it was there because when we you start the report it really shows the record set of the bookmarked vendor. So the best approach is to remove this field from the request form.

Also there is another catch to this. Classic reports are meant (in true Dynamics NAV spirit) for users to enter as many as parameters or values in the request form fields as possible. In this case, when using the Dummy Game, you can call reports for only one record, or better said for the bookmarked record. So my recommendation is to really think if you want to use the Dummy Game or not. In the end it depends on the client's business processes and business requirements.

Page Record Filtering - Bookmarking

Another way of calling reports from RTC is with record filtering, or setting bookmark on the page itself. Unlike the Dummy Game where all the "trick" code is customized on report itself, here we are setting filters directly on the page. The trick in this classic report call is to set a filter on an action, which is calling the report. But no report customization is needed. A specific action is used for calling the report C/AL code that has been inserted into the OnAction() trigger.

This code runs through all of the records visible on the page and remembers the one that you've bookmarked. This trick is may be better than the Dummy Game approach in the sense that it cannot mislead end users and it shows all bookmark data in request form fields. The only drawback of this method is that the user can see how RTC is running code on page and highlighting every row as it passes through. In this method the user can also edit values in request forms and insert values as he pleases.

And in conclusion, before using any of these methods, it is best to consider all pros and cons of using filtering. I share these methods based on my perspective of upgrading classic NAV to RTC - when the user already has the experience, knowledge and routine of using classic report. And when implementing classic reports for a new NAV RTC user I would always go for one of these methods, depending on nature of report (as opposed to upgrading the report to RTC?).

Dynamics World Support

I'm proud to say that portal Dynamics World has published my article about Dynamics NAV.

You can read blog directly on MSDynamicsWorld site.

Access NAV Server Through Multiple Different Domains

Accessing NAV Server Through Multiple Different Domains tends to be wery frustrating! Have you ever encountered situation where You needed to connect NAV RTC client from one domain to NAV Server which is on other domain? Well, I did. And I must say that this is kind'a BIG problem with international companies who have strong security policy.

Well, luckily Microsoft has server and infrastructure issues that came great in solving this problem.

When thinking about how to solve this problem main thing that came to my attention is how to transfer permissions from one domain to another with same users, and at the end how will those users authenticate to NAV server with Windows authentication. I must say that I was really surprised when I found out that windows recognizes users between domains as same users if they have same user name and password.

For start, lets assume that You have created users on NAV server which is in different organizational unit and different domain.

Active Directory Setup

Create users on Server in Active Directory with appropriate rights and in appropriate organizational unit.
When creating users remember that newly created users must have:

• Same username as users on NAV Server
• Same password users set up on NAV Server

When You’ve created user, just click Finish to apply newly created user.

To check if Your user is created as it should check your Organizational unit to see if Your new user is positioned in that Organizational unit.

SQL Server Setup

Create New login with Windows authentication. This user must be with same user name as the one on NAV server, but with domain where is SQL server.

Don't forget to Map user on appropirate NAV Database.

VIEW SERVER STATE on SQL ERROR

Now, users are created and theoretically they should be able to connect to SQL server – but not.
If You try to connect to database (and You have created users in NAV), You'll get View Server State Error.

Next thing is to set up Database properties and grant View Server State Permission to all users that need to connect to Your NAV Database.
To set up users edit Database Permissions on SQL Server Properties.

In upper part of Form You need to find user who You'll give that permission to. After You have found it You need to Grant Explicit permission to View Server State parameter in lower part of form.

Confirm setup with OK button and You're set.

Create Users in NAV

Following standard procedure in NAV create users with Windows Logins and with appropriate permissions.

 

When created, don’t forget to Synchronize them.

This principle is best used in companies who want to use NAV RTC client in their business, otherwise You can direct users to connect through Database logins.

Implementing Nmbering Series

Number series is feature in NAV that allows usage of numbering methods and also allows the application to work the same everythere.

This tutorial will explain how to implement Number Series in a new table or add them to existing table. First part of tutorial is focused on creating No. Series columns in tables, middle part of tutorial is focused on coding auomatization of No. Series and last part of tutorial is focused on creating function which will be used to drill down to numbering series line of our specific numbering series.

Another thing, best way for designing and developing NAV is using existing functions and code because they're already tested and probably working without bugs.

Step 1: Creating numbering series columns in a table

In our new / existing table You need to create this two columns (fields) which will be used for storing number series. First field (No.) needs to be created as primary key field.

Please name columns as in next table because of copying functions from other tables, and also this is standard naming policy for No. Columns and Number Series columns in NAV.

To create this fields, go to the object designer and create a new Table / design existing table.

Now our table should look like this.

Step 2: Compile table and add C/AL code

When implementing number series automation, there are some required pieces of code that you must include in your table:

1. OnInsert() trigger,
2. OnValidate() trigger for No. field,
3. AssistEdit function.

Whithout writing New code You can paste it from Sales Header Table and modify it, or decide to write you own code. It's up to you.

Before writing Code You need to create Function AssistEdit in Table C/AL Globals with return value Boolean, which you enter in Locals parameters of function.

After function is created you need to create link to No. Series Setup table for your table and NoSeriesManagement codeunit for automatization of number series which will be explained later in this article.

After table C/AL globals are created, compile table, close it and reopen it in design view.

NOTE: Reason for compiling table is because Rec and xRec still aren't validated by compiler and table data so you need to do so in order to write and compile table later. In case you forget this you need to save your new table without Compiled option, and compile it later through object designer.

Now you can start writing your code and when you're deone with modifying your code your new table should look like this.

Now, lets through every trigger and AssistEdit function and explain what they are going to do:

• OnInsert() trigger. Basicly here we write code which tests value in No. Field and if it's empty it calls our rcdSetup record (C/AL Global variable that links our table with table where we're choosing number series for our table nad form) and test if there is value in field „Br. serija za RC“ which is field developed for setting up number series for this project. If we have previously choosed number series we are calling codeunit NoSeriesManagement (C/AL global NoSeriesMgt) which is inserting next value from No. Series Lines table into No. Series and No. fields.
• No. – On Validate () trigger. Here we write function which tests if value in No. field is equal as one in No. Series Lines table. If it is not, then it sets value of No.Series to blank because of insert automation which is dependent on No. Series fields.
• AssistEdit function. This function is developed for purposes of DrillUp to form of No. Series form based on No. Series data of No. Series field of our table. Basicly it calls for NoSeriesManagement function to validate No. Series. Later, when developing forms and pages, this function will enable us to call No. series window with exact No. series value un field of No. of our form.

Step 3: Creating own numbering series

In our table we have added existing No. Series settings whtough rcdSetup C/AL Global parameter. If yuo want to create new number series setting which will be added to Purchase & Payables Setup. Ofcourse you can add number series setup to any other form.

First step is to create new table field which will be used for our purpose. Best thing is to copy and paste existing field for number series.

Now go to last row of table and paste selected column.

Rewrite Field No. to to match row order.

After modifying row of table be sure to check properties of table and TableRelation parameter which needs to be set to „No. Series“ because we used this value in our based table as value for No. Series relation.

If you decide to change this to another value than you need to update our first table with this value – only in C/AL code.

Step 4: Update C/AL code and C/AL globals in first table

After modification of table, you need to go back to our table and change Record parameter in C/AL globals and in C/AL code replace "Br. serija za RC" with „Implementing Nos.“.

Now our C/AL globals need to look like this:

And C/AL code needs to look like this:

Save the table.

Step 5: Create user interface

Last step in implementing our Number series functionality is to set user interface. This is done with OnAssistEdit() trigger on No. field. This will add new button in form field which will open form with No. seris of our setup table.

Create new card form with form wizzard or page with page wizzard.

Now enter C/AL code to trigger

When developing page change CurrForm with CurrPage and you're set.

Now let's test our form.

Enjoy..