For the Role Tailored Client, NAV doesn’t store the setup and configuration in the zup-file we know for the Classic client. This post contains a few small pointers to the location of these files.
Have you ever wonder what ‘The client version does not match the server version. You can only connect to a server with a matching version.’ error message really means? Since the error message shows the file (build) versions of the client and server it has been speculated that only clients and servers of the same build can connect, which is not the case. What really happens is that we have a communication interface between Microsoft Dynamics NAV Server and clients that has an internal version number which we change when this contract is broken (interface is changed so that it is not compatible anymore), and in that case the versions will not match and you will receive this error.
Configuration mode is a setting in Microsoft Dynamics NAV that allows you to customize the user interface (UI) for a particular role. It will enable an Administrator or Super User to customize a profile themselves and then assign it to different users. That way, the users (especially novice users).
When you start the Microsoft Dynamics NAV Windows client or the Microsoft Dynamics NAV Web client, a connection is established with the Microsoft Dynamics NAV Server instance, and a corresponding session is added on Microsoft Dynamics NAV Server. Microsoft Dynamics NAV Server includes several timeout settings that determine when a session closes because of inactivity, a lost connection, or the client closes.
n the RoleTailored client, operations such as RENAME and COPY fail if the destination for the file operation is not on the computer running Microsoft Dynamics NAV Server. One solution is to configure Microsoft Dynamics NAV Server to delegate on behalf of the RoleTailored client as described in this topic.