how to find out the custom module

While ModuleBuilder is a good place to start it may not show all the custom modules. Some developers remove the packages from ModuleBuilder to prevent re-deployment in a production environment which can have some serious unwanted consequences (you should never redeploy a module builder package after it was put in production

 https://support.sugarcrm.com/Knowledge_Base/Studio_and_Module_Builder/Best_Practices_When_Building_Custom_Modules/ ).

In general, modules built via Module Builder will have a characteristic name that starts with an alphanumeric key and an underscore that will prefix all of the directories, class names and table names of the modules in those packages.

Some developers and third party consultants prefix all their customizations the same way identifying the sugar instance or the company or person who developed the package, others vary prefixes and use it more as a package identifier, but in the end all the all will look something like:

xxxxx_SomeCustomModuleName 

while all the modules that come with a standard Sugar deployment are simple camel case names without prefix and underscore.

So if you have an on-site copy of your CRM you can look at <sugar-root>/modules/

those starting with a string and an underscore are almost certainly custom modules.

There are probably ways of building modules in code without such a key but I think it is unlikely.

Best of luck,

FrancescaS

While ModuleBuilder is a good place to start it may not show all the custom modules. Some developers remove the packages from ModuleBuilder to prevent re-deployment in a production environment which can have some serious unwanted consequences (you should never redeploy a module builder package after it was put in production

 https://support.sugarcrm.com/Knowledge_Base/Studio_and_Module_Builder/Best_Practices_When_Building_Custom_Modules/ ).

In general, modules built via Module Builder will have a characteristic name that starts with an alphanumeric key and an underscore that will prefix all of the directories, class names and table names of the modules in those packages.

Some developers and third party consultants prefix all their customizations the same way identifying the sugar instance or the company or person who developed the package, others vary prefixes and use it more as a package identifier, but in the end all the all will look something like:

xxxxx_SomeCustomModuleName 

while all the modules that come with a standard Sugar deployment are simple camel case names without prefix and underscore.

So if you have an on-site copy of your CRM you can look at <sugar-root>/modules/

those starting with a string and an underscore are almost certainly custom modules.

There are probably ways of building modules in code without such a key but I think it is unlikely.

Best of luck,

FrancescaS

Hi FrancescaS,

Thank you. I can see some module did follow the prefix. I found a module named Products and this one don't have prefix. I want to know more about this module, but I can't find any document related to this module on sugar website.