Getting Started Developing for SugarCloud

I'm trying to add an extra button into a listview header that will prepopulate a value in a dropdown list.

I understand I need to extend the list-headerpane folder for the module, and add the button in list-headerpane.php by extending it to custom folder "custom/modules/<module_name>/clients/base/views/list-headerpane/list-headerpane.php (although I assume this would just add the button, and I'd need to extend list-headerpane.js to add the functionality)

However, despite having read the Sugar 10.2 Developer Guide ( and the dev tutorials ( I'm still none the wiser on how to actually view and extend list-headerpane.php, and package it so it can be deployed to our development and integration environments.

Is there a beginners tutorial that covers this?

  • I've not done this myself and I'm not sure I understand what you are looking for, but to add a button in the list-headerpane in a given module I would edit the file you mentioned and add your button to the button array as follows


    $viewdefs['<module>']['base']['view']['list-headerpane']['buttons'][] =


                'name' => 'your_button_name',

                'type' => 'your_button_type',



  • Thanks for this, but what I'm looking is for is *how* you access and edit the file. I've tried downloading the files via the diagnostics tool but it doesn't include list-headerpane.php.

  • Do you have an On Demand of SugarCRM version?
    Becuase if you have it, you don´t have access to the SugarCRM core files, for that reason you don´t can edit directly the file.
    You must do an install file.
    The diagnostics tool don´t gives you the file because it hasn´t, You may be need overwrite it, so, You must to create the folder and the file in the route:
    Here you create the folder...
    list-headerpane and then the file: list-headerpane.php
    So, you must have and see:


  • If you are a Cloud customer, I suggest you download, and install a local instance of SugarCRM on a LAMP stack to get the core files. Do your development and testing on your local instance and then use Manifest to upload your tested changes to your Cloud instance. 
    You can find some guidelines here:

  • Thank you so much this is exactly the missing piece I've been looking for. Hugely appreciated thank you.

  • We're running a cloud instance (AWS EU West) of Sugar Serve Version 10.1.0. 

    There are many installer options to choose from- what is the correct on-prem version to install that corresponds to our cloud instance?