SugarCRM Troubleshooting: Install Time Problems

Sometimes weird things happen for a reason.  Here is a good example.

A few days ago, I decided to reset the database for a test installation of SugarCRM 5.5 that I have on my laptop.  By that I mean that I ran the installer again, my goal being to cause it to overwrite the already existing database.  My reason for doing so is that I wanted the demo data to test something for a project I was working on.

For those of you wondering how I went about getting the installer to run again, all I did was edit my config.php file and changed this:

'installer_locked' => true,

to:

'installer_locked' => false,

That modification to config.php allows one to run the installer again although the installation may already be operational.  Obviously you wouldn't want to do this on a regular basis as this process could potentially cause you to accidentally delete your SugarCRM data, but it does have its uses and thus is helpful to know.

Now, back to my situation.  After changing my config.php file, I proceeded to walk through the installation process as normal.  I filled in the various fields with the appropriate data and continued through the installation wizard without any problems.

Problems, however, did arise when I got to the final stage of the installation wizard while creating the database.

SugarCRM Customization: Read-only Fields

It is no secret that I am a big fan of the ease of which the SugarCRM framework facilitates a number of customizations.

A few months back I shared a simple example that demonstrated said simplicity quite well through a customization of the search popup windows. Let us take a look at another equally simple and useful modification.

This time around we are going to look at something just as easy, but serving a completely different purpose.

In this scenario we will assume that we have a need to create a read-only field, one that cannot be edited via the SugarCRM interface.  This is helpful for scenarios where records may contain important data that should not be changed by any user.  A good example of this is financial data from external systems, such as your ERP solution.

Because this data is coming from another system, it is usually input into SugarCRM by means of a link or other programmatic approach that eliminates the need for the user to actually enter the data by editing the record.

Allowing users to manipulate the values would create the potential for faulty analysis.  For example, if one of the values relates to a customer's outstanding balance, a user could accidentally (or purposely) increase or decrease it, in turn misleading the next person that views said record.  Hence the value of using a read-only field.

Converting a field into a read-only field is quite simple.  Read on to see the step-by-step instructions.