back to top

Clearing user default settings in the SalesLogix web client

Each user of the SalesLogix web client can define various user based  settings while they are using the SalesLogix web client.  Things such as splitter height, visible tabs, open tabs, etc are all stored per user.  Sometimes these settings block other changes that you would like to force out administratively.  For instance what if you decide you want to set the tab order on the account page to be a particular order?  Well for users who have never logged in, the next time they log in they will see this change.  however, users who have already used the system will not see the change.  This is because the user’s previous tab definitions have already been defined and stored.  These individual user preferences take precedence over the default settings.

 The settings are actually stored in the SalesLogix database in the VIRTUALFILESYSTEM table.  This is so that regardless of what computer the user logs into the web client with, the settings will carry across.  Now the VIRTUALFILESYSTEM actually contains pretty much everything that is the SalesLogix web client, including all of the entity definitions, screens, code, etc.

 Because of this and because it is just smart, I need to pause here and say: “PROCEED AT YOUR OWN RISK.  MODIFYING THE DATABASE AS DERSCRIBED BELOW CAN BE POTENTIALLY HARMFUL IF YOU DO NOT KNOW WHAT YOU ARE DOING.  PROCEED ONLY IF YOU UNDERSTAND WHAT YOU ARE DOING AND ALWAYS TRY THIS SORT OF THING IN A TEST SYSTEM FIRST”.

 OK Now that this disclaimer is out of the way, you can find all of your users default settings stored in the VirtualFileSystem by running a query similar to:

Select * from VIRTUALFILESYSTEM where modifyuser = ‘{USERNAME}’ and itemname<>’{USERNAME}’

 The query above needs to be updated to have {USERNAME} changed to the SalesLogix username like “lee” for Lee Hogan.

 

Now to clear all of the user settings you can run a query like:

 

Delete from VIRTUALFILESYSTEM where modifyuser = ‘{USERNAME}’ and itemname<>’{USERNAME}’

After executing the script you would need to do an IIS reset to clear the old settings from the IIS cache.

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Kris Halsrud
Kris Halsrud
Kris Halsrud is a Senior Analyst / Developer for Customer FX Corporation.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos