In previous versions, all local client settings are stored in the .zup file. In Microsoft Dynamics NAV 2009, this is a bit more complex. This post tries to describe which settings are stored where.<\/p>\n
In addition to that, with NAV 2009 you may be spending a lot of time looking for files with long folder-names. So this post also shows you the location of each file, to make it quicker to find them.<\/p>\n
\/\/\/ Blog updated October 2nd: Section “temporary server files” updated with path for Windows Server 2003.<\/p>\n
In NAV 2009, settings are stored in various places. The following lists what is stored where. some settings are stored in files, and some in tables. I hope I have included everything here. But if the list should be incomplete, I would appreciate comments at the end of this post.<\/p>\n
PersonalizationStore.xml<\/strong> This file stores some personal settings for the client like resizing of columns. It is probably the closest thing to the old zup file there is. The data in this file is primarily binary because it it not supposed to be updated manually. Even if you could edit the file (if you could find the settings you wanted to edit), then this is unsupported. But, like the old zup file, you can delete or rename it, and next time the client opens, it will create a new one.<\/p>\n ClientUserSettings.Config<\/strong> This file is where you can set RTC to connect to a specific service tier and\/or a specific port.<\/p>\n CustomSettings.config temporary Server files \/\/\/ Update<\/p>\n The path above is for a Vista OS. If you run NAV server on Windows Server 2003, the path is:<\/p>\n C:\\Documents and Settings\\All Users\\Application Data\\Microsoft\\Microsoft Dynamics NAV\\60\\Server\\<\/p>\n \/\/\/ —–<\/p>\n The service tier uses this folder for various temporary files. It is definitely not recommended to change any files here! But it might be a place for troubleshooting certain problems (though I am not sure what kind of problems).<\/p>\n 2000000075 – “User Metadata” 2000000071 – “Object Metadata” In previous versions, all local client settings are stored in the .zup file. In Microsoft Dynamics NAV 2009, this is a bit more complex. This post tries to describe which settings are stored where. In addition to that, with NAV 2009 you may be spending a lot of time looking for files with long folder-names.<\/p>\n","protected":false},"author":4528,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ms_queue_id":[],"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","footnotes":""},"post_tag":[],"product":[],"content-type":[18],"topic":[],"audience-type":[],"audience":[],"ms-author":[],"coauthors":[4273],"class_list":["post-42733","post","type-post","status-publish","format-standard","hentry","content-type-thought-leadership","review-flag-1593580425-950","review-flag-and-o-1593580421-190","review-flag-new-1593580245-522"],"yoast_head":"\n
\nstored in:
\n%AppData%\\Microsoft\\Microsoft Dynamics NAV\\<\/p>\n
\nStored in:
\n%ProgramData%\\Microsoft\\Microsoft Dynamics NAV\\<\/p>\nServer side:<\/h4>\n
\n<\/strong>stored in (default):
\nC:\\Program Files\\Microsoft Dynamics NAV\\60\\Service\\
\nThis is where you set up parameters for the Service Tier like SQL Server name, Database name, port number etc.<\/p>\n
\n<\/strong>Stored in:
\n%ProgramData%\\Microsoft\\Microsoft Dynamics NAV\\60\\Server<\/p>\nTables:<\/h3>\n
\nWhen you go to “Customize this page”, then it’s stored here.If for example a user ads new parts, like a chart or does anythign else herel,this table contains one record for each urse, for ach pae that they have persinalised.<\/p>\n
\nThis table stores all the objects for RTC. Whenever you compile an object, it transforms it to a format that is designed for RTC and stores it in this table. You can delete entries here, though I would not recommend it. But if you do, and want it back, then compile the missing object from Object Designer. The data in this table is generally binary, so also not something to modify and definitely not necessarily supported or documented.<\/p>\n","protected":false},"excerpt":{"rendered":"