SalesLogix 7.5 field security – Issues with bundled changes

I have noticed that SalesLogix has a problem when delivering customizations to a system via a bundle when the bundle contains changes to the database structure, specifically adding fields to existing tables.  It does not seem to matter if you use a "create table" or "create field" command.  When the bundle is installed the fields install correctly into the database and work fine when using the admin login.  For other users, however the new fields act as though there is a read-only field security profile in effect for the new fields (Users can see data that is in the field but if they try to edit it it acts as a read-only field in the LAN client).

To fix this problem all you need to do are the following steps:

1. Log into the admin as admin.  (If you have just installed a bundle you obviously can skip this step.)
2. Go to the "Manage…Field Security Profiles" in the administrator menus.
3. When the Security Profile Manager" dialog appears, simply press OK.

There, pretty simple.  You do not even need to actually edit any of the field security profiles.  This is a good thing, as some levels of SalesLogix prevent you from modifying field level security profiles.  Apparently when the OK button is pressed the system "refreshes" the field security definitions, and any new fields correctly get the read-write security by default.

Preventing issues with newly installed fields is not difficult though it does require an extra step after installing a bundle.  It can save a lot of hassles down the road so I recommend that whenever new database fields are added through a bundle, always do the extra step of "refreshing" the field security cache.