Author avatar for jason

SugarCRM 7 - Passing Data to Views

Posted by on November 13, 2013

Last week we covered how to add a global menu item in SugarCRM 7. Today we will expand on that example by passing data to the menu item to make the URL built specifically for the user who is currently logged in.

In this SugarCRM instance a custom field has been created in Studio called “wiki_user_c”. This is what we need to pass along to the view in order to display the correct URL. To pull that data, the first step is to copy over /clients/base/views/profileactions/profileactions.js to /custom/clients/base/views/profileactions/profileactions.js. Within that file we alter setCurrentUserData to pull over our custom field:

The next step is to tell the app how to load that field via the API. The new client API makes it really simple to extend any method. In this case, we want to extend the retrieveCurrentUser method from CurrentUserApi. In the example bleow, our endpoint is first registered. The below in retrieveCurrentUser() some code is thrown down to pull and pass that data along. Since this is extending a core API make sure to call the parent so that no existing functionality is affected.

/custom/clients/base/api/WikiCurrentUserApi.php:

Finally, alter the .hbt template in /custom/clients/base/views/profileactions/profileactions.hbt to use the new wiki_user variable:

Run a Quick Repair & Rebuild and then refresh the browser to see the changes. The rebuild will cache our custom endpoint in /cache/include/api/ServiceDictionary.rest.php and will be given a score to help give it preference over any other endpoint. In this case, the default CurrentUserApi endpoint.

The big issue that we face with this method of altering the profileactions view in the custom directory is that someone down the road may also customize that view. Similarly, our solution may completely overwrite an already existing profileactions change on a given SugarCRM instance.

To minimize these potential issues we'll look at a few different options next week including extending the core javascript object and defining a new view to be loaded in place of profileactions.

Like this post?

We'll send you an email once a month with the latest posts.

Keep up to date on the latest additions

We'll send you an email every month with handpicked add-ons, reviews, tricks and tips. Don't worry, we hate spam as much as you do.