how to find out the custom module

RE: how to find out the custom module

Manson ho — Mon, 21 Mar 2022 05:28:48 GMT

Thank you so much! I got a direction now.

RE: how to find out the custom module

Manson ho — Mon, 21 Mar 2022 05:28:43 GMT

Thank you so much! I got a direction now.

RE: how to find out the custom module

John Hawkins — Thu, 17 Mar 2022 11:01:19 GMT

Manson ho

Unfortunately, as you have seen from the multitude of answers here, there is no "one size fits all" method of determining which modules are custom build versus which are core Sugar modules I'm afraid. To add my thoughts, there are a couple of ways I would use to find this information.

Firstly, the option is there to create a clean install locally of an instance and within that you can see what are the "core" modules. If you are on-premise, or can get a backup to restore from, you can use diff tools to do some checking as well.

A second option would be to inspect the files at: ./include/modules.php and ./custom/application/Ext/Include/modules.ext.php - which should contain the definitions for the global arrays for $beanList and $beanFiles. The entries in the file under the custom directory will tell you which beanList items have been added as custom objects and the one under ./include/ will be the core file that defines the original list. Of course, the core file is only available if you are on-premise or you have a backup to inspect (easy enough to get). However, you can download the full contents of the ./custom directory using the Diagnostic tools in the Admin section if you are on-Cloud.

Hopefully some combination of all these techniques you have been shown in this thread will lead you to the information you want 🙂

Thanks,

JH.

[EDIT]

P.S. In the custom version of the files you will get all "non-core" modules listed. This will include not only those that have been custom built for your instance but also those added as part of an extension package, such as Hint, SugarChimp, Customer Journey Plugin etc.

I don't think there is an easy way of determining the difference in the code files without understanding what you have. However, the ones installed from an extension will probably have an entry in the Module Loader list whereas ones added via a deploy from Module Builder (even if the package has subsequently been deleted from there) will not.

RE: how to find out the custom module

Francesca Shiekh — Thu, 17 Mar 2022 01:58:07 GMT

Some Sugar modules have changed names through their history but retained the directory names...

The "Products" module in the code is "Quoted Line Items" in the interface. "ProductBundles" are part of that too, they group quoted line items into groups which affect subtotals etc...

The Quotes architecture is not as easy to understand as some other modules, at least not for me.
There is a lot of documentation here that will help you understand the relationships between Quotes, Products, and ProductBundles:

https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_11.0/Architecture/Quotes/

If you have any difficulties, don't hesitate to search or ask questions around the Developer Community, I've found a lot of helpful answers here over the years :) and we all have to start somewhere!

RE: how to find out the custom module

Manson ho — Thu, 17 Mar 2022 00:58:03 GMT

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.

RE: how to find out the custom module

Manson ho — Thu, 17 Mar 2022 00:56:58 GMT

Hi Vijay Kumar,

Thank you. I am checking now.

RE: how to find out the custom module

Manson ho — Thu, 17 Mar 2022 00:56:16 GMT

Hi Fred,

Thank you for help.

it's empty.

RE: how to find out the custom module

Francesca Shiekh — Wed, 16 Mar 2022 13:36:37 GMT

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

RE: how to find out the custom module

Vijay Kumar — Wed, 16 Mar 2022 07:35:11 GMT

Hi, Manson ho,

Please follow the guideline of this blog: SugarCRM Module

you can easily find it on module builder(administration section)

RE: how to find out the custom module

Frédéric Rinaldi — Wed, 16 Mar 2022 07:22:47 GMT

Hi Manson ho,

did you also check the module builder (from the administration section) ?

Fred