Extending Views is fun and easy to do, but did you know there is a right way and a wrong way to extend module views.  Well I shouldn’t say wrong as it still works but it’s non-upgrade safe, and from my experience it will cause you headaches after you do an upgrade and something is not working correctly.  Click Read More to see what I’m talking about.

Recently I began working on some custom scripts to export workflows.  I wanted to make this int a module loadable package so it’s easy to install and use.  I was looking around to how to add the files to the admin without having to build a full on custom module since I just need one screen with some options.  I was looking into how to extend the action_view_map.php file in the Administration module and I came across a bit of code that I figured would be useful to share.

It’s been a little over two years since I started at SugarCRM. While it’s been a fun ride in Internal Applications (iApps), it was time for a change. I’m not leaving Sugar, but I’m moving to Core Engineering to help make the product that much better.  This change is needed for me, I was getting antsy doing the same thing day in and day out.  I’ve learned a lot about how the app works from a customization stand point and I feel that I can bring that knowledge into Core and help make the product better for customizers and end customers using the application.

Here is the the next phase of my time at SugarCRM!

And if you are looking for a job, SugarCRM is a fantastic place to work and you should check out our job listings and apply today!

Have you ever had a user complain that items are not showing up in the History Sub-Panel?  Here are SugarCRM we have had that problem a few times since upgrading to 6.4.  Lucky for us this is an easy problem to solve.  Click on read more to find out how to do this.

While getting ready to take stuff live for a project I came across an issue, there is no way to export workflows definitions in SugarCRM from our development environment, so we wont have to recreate them in our production environment. Updated: three issues have been fixed, click read more to see the details.

Have you ever wanted to set up a Global ACL Policy for users in SugarCRM?  I wanted to this past week and found with the lack of a global group it was very confusing at first.  The reason for this was that we developed a module that controls LeadRouting and we wanted to enabled Sales Managers to control who got assigned for a given state in the US and Canada or by a given country everywhere else.  Since we didn’t want people updating this module unless they were in Sales Management we need to lock down the whole module.

I’m proud to announce the v1.0 release of SugarFieldWorklog.  I have spent many hours refactoring the Worklog SugarField to have it store the entries as Notes related to the parent module.  This allow for greater support going forward and will allow more flexibility in future releases for what the Worklog field can do.  Click Read More for the list of changes in this release and download links.  Update: Version 1.1 has been released to address a couple of issue that I found post release.

Welcome to the first Jon’s Tips and Tricks for SugarCRM.  In this post I’m going to cover how make fields required when other fields equal something specific.  Now I know what you are going to say, “This is available in studio” and while it is, it will hide the field on the edit view when you don’t have the values selected/set in the specific control fields.

This is done though a vardef (variable definition) extension in Sugar and it’s an upgrade safe customization.