Comments on: How to reset field values on bean duplication?

By: Joe Hines

Joe Hines — Wed, 27 Jun 2012 04:39:48 +0000

The information in your post about SugarCRM Development is very interesting and very helpful for the Developers for the SugarCRM Development.

By: João Morais

João Morais — Fri, 15 Jun 2012 09:17:07 +0000

Hi @Matthew, @Jeff Bickart,

This article was rescued from my blog backups, so it was probably obsolete, unfortunately I lost a few posts due to unpredicted hosting issues.

Thanks for your feedback guys
Already updated the post in order to reflect the changes you guys pointed out, and also gave you credits for that.

Regarding the “truly” custom views, I think that this feature was implemented in the latest versions, from what I recall at least in SugarCRM 5.2.X it didn’t exist, and one was forced to copy all their logic to the ones on custom folder.

By: Matthew

Matthew — Thu, 14 Jun 2012 12:25:53 +0000

Very nice, Joao. The only thing to add is that not all beans have a specific view.edit.php file in their directory. Some do and some don’t… for those that do, the new class is usually CustomViewEdit and it would extend ViewEdit. For thost that don’t, they’ll extend the normal ViewEdit but they can (and probably should still be) named CustomViewEdit.

By: Jeff Bickart

Jeff Bickart — Thu, 14 Jun 2012 12:17:14 +0000

There a few corrections to be made to your post. When you create a custom view.edit.php in custom/modules//views/view.edit.php and your new class should be called CustomViewEdit not ViewEdit.

Further you usually don’t need to copy the logic from the modules//view/view.edit.php you should be extending it.

So a custom Contacts View edit would be

require_once(‘modules/contacts/view/view.edit.php’);
class CustomContactsViewEdit extends ContactsViewEdit

Changing it in this manner allows for the core code to be changed from SugarCRM Version to SugarCRM version and not loose any functionality