Day 1 helped you understand the fundamentals of SuiteCRM, specifically SuiteCRM field types, its core modules, and how it manages records. Day 2 is about CRM advanced, and this is
Day 1 helped you understand the fundamentals of SuiteCRM, specifically SuiteCRM field types, its core modules, and how it manages records. Day 2 is about CRM advanced, and this is where we will shift gears. Today, you are entering the engine room, where you will understand the true capability of SuiteCRM: developing custom modules from scratch, transforming the present ones without modifying a single line of code, and establishing relationships that make your CRM resonate with how your business actually operates.
Let us walk through three closely connected tools, Studio, Module Builder, and the Extension Framework. We will also explore the types of relationships that synchronize your data. At the end of Day 2, you will not only understand the working of these tools but also when you have to use each one, and how they effectively work together, which enables you to create a CRM that resonates with your processes instead of forcing your processes to adjust to your CRM.
Module Builder
Module Builder (Admin → Module Builder) creates entirely new, custom modules from scratch. Use it when no existing SuiteCRM module fits your data model.
- Package: A container that groups one or more custom modules for deployment. Packages are exported as .zip files and installed via Module Loader.
- Module: A single custom entity inside a package. Gets its own database table, ListView, DetailView, EditView, and Studio configuration.
- Deployable: Once deployed, the module behaves identically to native SuiteCRM modules and is fully customizable via Studio.
Studio
Studio (Admin → Studio) customizes existing modules — add fields, rearrange layouts, manage relationships — without code.
- Fields: Add, edit, or remove fields on any module. Custom fields land in the _cstm table with a _c suffix.
- Layouts: Drag-and-drop editor for EditView, DetailView, ListView, SearchView, and the Quick Create popup.
- Relationships: Create 1:M or M: M relationships between modules. Studio handles the SQL schema, vardefs, and subpanel configuration automatically.
- Subpanels: Configurable related-record panels shown at the bottom of a DetailView (e.g., Contacts subpanel on an Account).
After any Studio change, run Quick Repair & Rebuild (Admin). Repair: Quick Repair & Rebuild to regenerate caches. Without this step, your changes may not appear in the UI.
Relationship Types — Deep Dive
| Type | Storage | Common Example | Created Via |
|---|---|---|---|
| One-to-Many (1:M) | Foreign key on child table | Account → Contacts (account_id on contacts) | Studio or vardefs |
| Many-to-Many (M:M) | Relationship junction table | Contacts ↔ Calls (calls_contacts table) | Studio or vardefs |
| One-to-One (1:1) | Typically 1:M with UI constraint | Rare — custom implementation | Code only |
Extension Framework
The Extension Framework is how SuiteCRM handles upgrades safely. All customizations go into the custom/ directory, never in core files.
Custom/Extension/modules//Ext/Vardefs/: Add or override field definitions.
Custom/Extension/modules//Ext/LogicHooks/: Register logic hooks for a specific module.
Custom/Extension/application/Ext/LogicHooks/: Register application-wide hooks (login, etc.).
Custom/Extension/modules//Ext/Language/: Add or override language strings.
Conclusion
You now have seen how the customization layer of SuiteCRM works from absolute scratch. Module Builder enables you to develop fresh entities when no off-the-shelf modules align with your business needs. Studio allows you to transform your present modules, layouts, fields, relationships, and subpanels via a point-and-click interface, with zero risk to core code. And the Extension Framework makes sure that everything you develop exists in the custom/directory, so when upgrades happen, your work remains intact.
Day 3 continues our discussion and delves deep into CRM advanced concepts. You will learn how to make your CRM react, i.e., automatically updating records, sending follow-up emails on a schedule, and secure endpoints so external tools can align with SuiteCRM. Up until now, you have put the pieces in the right place; on Day 3, you will see how they work together.
Respond to this article with emojis
