Update on CreateActionsView changes in Sugar 7.7

Matthew Marum —  December 29, 2015

Based on Sugar Developer community feedback, we have an additional update about the CreateActionsView changes in Sugar 7.7.

CreateActions migration script added to Sugar 7.7 Upgrader

During Sugar 7.7 upgrade, the upgrader will identify existing create-actions view/layout customizations and automatically migrate them to create view/layout.  This is a best effort migration that follows the two steps listed near bottom of this blog post.

If a custom create view/layout already exists, then create-actions changes will not be automatically migrated.

This will mitigate impact of this change for existing Sugar customers.

Matthew Marum


Matt is the Director of Developer Advocacy for SugarCRM. Previously he was an Engineer on Sugar 7 and a Solutions Architect for the OEM program. He is also an avid trail runner, Boston Marathon qualifier and a karaoke aficionado.

5 responses to Update on CreateActionsView changes in Sugar 7.7


    Will there be a way to keep a distinct view for Quick Create?
    Currently we can use create for Quick Create, and create-actions for “full” create.


      Yes, Quick Create continues to use the Quick Create menu metadata to select the layout to use in the drawer.

      For example, in modules/Accounts/clients/base/menus/quickcreate/quickcreate.php

      $module_name = ‘Accounts’;
      $viewdefs[$module_name][‘base’][‘menu’][‘quickcreate’] = array(
      ‘layout’ => ‘create’,
      ‘label’ => ‘LNK_NEW_ACCOUNT’,
      ‘visible’ => true,
      ‘order’ => 0,
      ‘icon’ => ‘fa-plus’,

      The ‘layout’ property selects the Sidecar layout to load when quick create is called. You could select a different create layout for your custom Quick Create by overriding or extending this menu metadata.


    Great! So no need to worry about the existing implementations…..:)


      Most existing implementations should migrate automatically. There could be issues if there are already existing “create” customizations or if the customized “create-actions” controller extends from a different controller than we expected.


    Hi Maat,

    Just wondering we will still be having the ‘Save and View’ , ‘Save and Create’ buttons in future? And what will happen if I have modified the button metadata of create-actions view (through Extensions) in such a way that ‘Save and View’ button will come as primary (I meant the default button)?