How to NOT update clientusersettings.config ?
mgn
Member Posts: 39
Is there a way to NOT automatically update the clients clientusersettings.config file?
When changing a server in the Windows client, the clientusersettings.config file is automatically updated by the client. Keys like "ServerInstance", "UrlHistory" and "UnknownSpnHint" are updated. The next time the Windows client is opened a connections is made to the value in "ServerInstance".
I prefer not to change these keys. The file does not change when I set the file property Read-Only, but then an error is raised in the Windows client when connecting to another service. Is there a way to give the user the ability to open any service instance (without errors) and not update the clientusersettings.config file?
When changing a server in the Windows client, the clientusersettings.config file is automatically updated by the client. Keys like "ServerInstance", "UrlHistory" and "UnknownSpnHint" are updated. The next time the Windows client is opened a connections is made to the value in "ServerInstance".
I prefer not to change these keys. The file does not change when I set the file property Read-Only, but then an error is raised in the Windows client when connecting to another service. Is there a way to give the user the ability to open any service instance (without errors) and not update the clientusersettings.config file?
0
Answers
-
I don't know how to do that, but a workaround would be to have a copy of the clientusersettings.config, and put some code in Codeunit 1 (or Codeunit 40 - Login Management) that overwrites clientusersettings.config with the copy.
Of course, if you ever DO want to change the values in clientusersettings.config you would also need to change the copy.Alastair Farrugia0 -
So, in other words, your real requirement is to make sure that each time the user starts the RTC the client connects to some preferred NST, rather than to the most recently opened one, right?When changing a server in the Windows client, the clientusersettings.config file is automatically updated by the client. Keys like "ServerInstance", "UrlHistory" and "UnknownSpnHint" are updated. The next time the Windows client is opened a connections is made to the value in "ServerInstance".
I prefer not to change these keys.
If this is the case you can look at the RTC command-line parameters, edit the shortcuts and add predefined server address there.
Slawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-030 -
Thanks Slawek, that seems to be solution.
I remember I tried this option some years ago and then I ran into some limitations. It seems that some parameters have been added and those issues are solved.
Next time I will be more clear when asking a question
. 0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 322 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
