Scripts are usually safe
Posted By: nicocrm on February 24th, 2011 in Uncategorized
No Gravatar

I think I just found the most awesome warning message ever. I am going to write all my dialogs like this too now. “Deleting an account is usually safe. Are you sure you wish to delete this account?”

Scripts are usually safe

SalesLogix Web – Installing Desktop Enhancements
Posted By: Alex.Cottner on February 16th, 2011 in Saleslogix
No Gravatar

The SalesLogix Desktop Integration Components are required for features like Drag and Drop, Mail Merge, SendSLX, etc. This can be installed from the SalesLogix login screen.

Note that Windows Vista/7 users may need to install this with ADMIN privileges.

On the Login screen of your SalesLogix Web Client, you will see the following…


SugarCRM – Menu Items Open in a New Tab/Window
Posted By: Alex.Cottner on February 15th, 2011 in General, Programming, SugarCRM
No Gravatar

The following is a simple example of making a menu item in SugarCRM (an item from a menu.php file) open in a new window. I needed a simple solution for this in order to integrate JasperReports Server.

$module_menu[]=Array("#\" onClick=\"'your_url_here');", $mod_strings['LNK_NAME'],"Image_Name", 'Module_Name');


Populate an extension entity in SData
Posted By: nicocrm on February 12th, 2011 in Saleslogix
No Gravatar

Quick tip – if you want to populate an extension entity (C_CONTACT_EXT or such), you don’t need to save it separately, you just need to pass the values as part of the “CONTACT” payload.  Note that you still need to have the “CContactExt” entity published to sdata (i.e. check the “Generate SData Feed” box in App Architect) for it to be available as part of the contact.

For example, using the C# client library:

var sru = new SDataSingleResourceRequest(_ws);
sru.ResourceKind = "contacts";
sru.ResourceSelector = locator;
AtomEntry entry = sru.Read();
SDataPayload contact = entry.GetSDataPayload();
SDataPayload contactExt = (SDataPayload)contact.Values["CContactExt"];
// note the values of CContactExt will NOT be read by default... you only retrieve a "shell"
// but you can pass new values.
// this works whether or not the "C_CONTACT_EXT" record already exists.
contactExt.Values["Nickname"] = "New Nickname";
sru.Entry = entry;

It’s kind of in the documentation but you have to read between the lines.

Lock down the Mass Update form
Posted By: Alex.Cottner on February 10th, 2011 in Programming, SugarCRM
No Gravatar

Something that I find very quirky with Sugar is the fact that they allow the Mass Update form to be accessible for all users. This can cause serious problems with data integrity if you let end users have the kind of power this form has.

When browsing Sugar’s forum I see topics all the time about how to remove or lock down the mass update form based on specific users, teams, or remove it entirely. There are a couple of different ways of doing this. A few include non-upgrade safe ways because we have to modify core files, and 1 is an upgrade safe way.