Role Tailored Client is the one of the best things that Microsoft Dynamics Nav 2009 brings, and if you are not using it, you are really missing out. It is tailored to your workers needs, inch by inch, making them more productive and less busy. Recently, I have been assigned by my firm to implement and install Role Tailored Client, and use it as our primary tool for accessing the Navision database. With the help of our partners, we have already switched to version 2009 r2, but never used RTC or tried to implement the 3 tier architecture in our firm. Few days ago we have finally finished implementing and installing Role Tailored Client in 3 tier architecture model, and in this post I would like to share some of the key points that I have learned googling the internet and reading many articles on this subject, and using some of my own skills to make it work more smoothly in our environment.
Here are some basing things that I have learned while implementing RTC:
- Middle tier on client computer - Role Tailored Client is build as thin client and it needs a middle tier server that will process the information from SQL server. It is suggested that for the best performance, Microsoft Dynamics Nav server should be installed on the client computer and then directed to the real sql server. Also, it is possible to create as many instances of the Nav server as you want, and even put them on the server where SQL server resides, but keep in mind that you will need a really good server too keep up with demand of the clients, especially if you have many people using Nav at the same time.
- No support for database users – Role Tailored Client only works with Windows authentication either local or domain based. The best practice is to add all your employees to a domain and then set up permissions as it fits your needs. After creating domain/local user, you need to add him to the database using Nav classic client, giving it permission to connect and to work on it.
- Giving Nav server right permissions – It is essential for any good implementation of Nav server that you give the right permissions for working with the SQL database or it just won’t work. You may get many errors if you don’t do this right. My advice is to always use least privilege permissions that you need to read write to certain database and to always use Navision tools to do it.
- Customizing roles is the key - Many people at the start will tell you that they don’t really need it or just won”t adjust to the new environment, but its your job to show them that its for their benefit. Customizing the views, role center and menus is the key for good user feedback and satisfaction.
Three step setup:
Role Tailored client can be easily implemented in just three steps if you already have a database that has Nav 6 objects in your database or simply put, if you can use the new Classic client with your database. Here are the three steps:
- Install Navision 2009 R2 on client computers with the following components: RTC Client, Classic client and Nav server. In the last step, click on the configuration screen of the Nav server and input the correct adress of your sql server and database name.
- Connect to your production database with Microsoft Dynamics Classic client and add local/domain user in the security> Windows users tab, and then set the appropriate user rights. Synchronize all logins.
- Setup Microsoft Dynamics Nav service to connect to the database with that username and password ( from run > services.msc , find Microsoft Dynamics Nav server and click properties). If you are not using domain in your network, you can connect as a local user.
Thats it! Start your Role Tailored Client and have fun using it!