Automating Custom Module/Field Creation

[craigotis]

Hey all,

We're writing a web application that uses SugarCRM as its back-end. We use Studio and Module Builder to create custom modules and fields in our test SugarCRM environment.

When we distribute the application to clients, we don't expect them to create these custom Modules and Fields themselves, as it would be very tedious, error-prone, and time-consuming. Our web application connects to SugarCRM over SOAP.

Is there any way to automate the creation of custom Modules or Fields? Either over SOAP or through some other method? (Scripting, Importing, etc.)

Thanks,
Craig

[davidboris]

Hello,

Can you explain your issue a bit clear? I'm little confused..

[Angel]

Hey all,

We're writing a web application that uses SugarCRM as its back-end. We use Studio and Module Builder to create custom modules and fields in our test SugarCRM environment.

When we distribute the application to clients, we don't expect them to create these custom Modules and Fields themselves, as it would be very tedious, error-prone, and time-consuming. Our web application connects to SugarCRM over SOAP.

Is there any way to automate the creation of custom Modules or Fields? Either over SOAP or through some other method? (Scripting, Importing, etc.)

Thanks,
Craig

You could do it via a manifest file which the user could apply via the Module Loader. Take a look at the Wiki and Developer site for more info on its syntax, etc.

sugarcrm.com/wiki
developer.sugarcrm.com

[jnassi]

For the custom module, within Module Builder you can "Publish" the package. That's the option intended for distributing the package to other people to deploy within their own systems.
http://www.sugarcrm.com/crm/support/...n.html#1670512 (look for the Publish section)

For the custom fields on existing modules, within Studio you can "Export Customizations".

http://www.sugarcrm.com/crm/support/...n.html#1670624 (look for the section titled Exporting Module Customizations)

You could conceivably take both of the two methods above and combine them into one distribution.

[craigotis]

Thank you very much for the replies, I'll be sure to check back with our results.

[craigotis]

For the custom module, within Module Builder you can "Publish" the package. That's the option intended for distributing the package to other people to deploy within their own systems.
http://www.sugarcrm.com/crm/support/...n.html#1670512 (look for the Publish section)

For the custom fields on existing modules, within Studio you can "Export Customizations".

http://www.sugarcrm.com/crm/support/...n.html#1670624 (look for the section titled Exporting Module Customizations)

You could conceivably take both of the two methods above and combine them into one distribution.

jnassi, I think this is the method we're going to attempt. Just to be sure, when we export the customizations to existing modules ("Contacts", for example) and our customers import those customizations, does their SugarCRM instance only pick up the additions? If they have their own custom fields that weren't present in our database, their changes won't be overwritten by ours, correct?

[Angel]

That's correct. It won't reset the module and then apply your customizations. Of course, the danger does exist that you could have a field name in your list that matches a name that the customer already defined, so you probably want to come up with some naming convention that minimizes those potential conflicts.