Archives For Studio/Module Builder

If you were at UnCon in April 2015 then you know that one of our hottest topics was plans for a SugarCRM Mobile SDK.  Since mobile devices and mobile use cases are such a key part of what Customer Relationship Management and Customer Experience is today and will be in the future, we are planning to enhance the SugarCRM Mobile development platform available to Sugar Developers.  You can follow the blog here for updates on that as they become available in the future.

However, there are already many different ways that developers can customize the behavior of the existing SugarCRM Mobile application today.  That will be the focus of today’s post.  In fact, you can drastically customize the behavior of the SugarCRM Mobile application without the hassle of having to distribute any custom code or apps to end-user Mobile devices.  All these techniques listed below involve only Sugar 7 server side code and metadata customizations.

Continue Reading…

This post is targeted at beginner to intermediate Sugar Developers who want to add a subpanel to a module which returns custom results.

This post assumes some basic knowledge of Sugar 7 development, Sugar 7 administration, PHP, and SQL.  This article will hopefully be useful to those who have done some Sugar 7 development but are not necessarily experts.

The example in this post was created on an out-of-the-box installation of Sugar Professional with the generated demo data.  But this technique should work on any on-premise Sugar 7 instance.

An acknowledgement

I recently needed to add a subpanel to a module which returned rows matching some unusual criteria.  The requirement for this subpanel didn’t match the standard one-to-many or many-to-many relationship with another module that a subpanel usually reflects.  I researched ways to do this and came across an excellent blog post on the subject by Shane Dowling.  Following what he had written I was able to accomplish my task.  This post is an attempt to make this technique accessible to those who are less familiar with Sugar 7 development.

Continue Reading…

In a recent blog post by W-Systems, an Elite SugarCRM Partner, the W-Systems team shows a great example of how to create a custom field type in Sugar 7 that allows you to place specially formatted text within a view.

This loadable module creates a new field type that allows you to format specific text on a record view to make it more noticeable to the reader. For instance if you want to bring special instructions or alerts to the record reader you may want to increase the text font size, change the font color or font background.

This custom field type is a great way to place in-line notifications on the Sugar 7 user interface.  You can also add as many as you want to the same view via Sugar Studio as you can see in the screenshot below.

Example of the custom field showing formatted text on a Sugar 7 Record View

Example of custom field showing formatted text on a Sugar 7 Record View

Custom fields allow Sugar Developers to get a lot of mileage out of a little work.  Developers focused on CRM implementations or who rely on the help of non-programmers to do Sugar administration and configuration should think about how they can use custom field types to get their projects done faster while using less code.

Head over to the W-Systems blog to find out more and try out this package for yourself!

There was a discussion recently in Andrea Ayer’s Sugar Adminstration Essentials class about previous layouts are stored in Studio when changing how a screen looks. You can access it on an View edit screen by clicking ‘View History’…

Screen Shot 2014-06-18 at 4.45.54 PM


The specific question came up of how many previous layouts are saved. Here’s the answer…

  • By default, the past 50 layouts are saved
  • You can change this by setting the config variable $sugar_config[‘studio_max_history’]
  • Setting $sugar_config[‘studio_max_history’] to 0 will enable saving all previous layouts