How to show meetings in every Invitee related Accounts Subpanel

My first instinct would be a custom Dashlet in the Intelligence Pane of the Account Detail View.

You can use a custom API to build the content: loop through the Contacts related to the Account and for each Contact get and display the Meetings that that contact is a participant of.

You can choose to organize/group the data by Meeting (date, list of participants) or by Contact (which may duplicate meetings if more than one person from this Account attended). I would probably choose the latter and allow the user to filter by date so you don't pull in years of historical data that may not be so relevant.

Keep in mind that the dashlets load regardless of whether your Intelligence Pane is open (I wish they would pull only when that particular dashboard is opened), so the loading of the record could be somewhat slower depending on how you build the dashlet, how much data you pull in etc...

By pulling this data into a Dashlet you can also make sure that it's loaded only for those people who really want/need to see it. Others will simply not add that dashlet to their view.

I'll be interested in seeing the solution you come up with.

FrancescaS

My first instinct would be a custom Dashlet in the Intelligence Pane of the Account Detail View.

You can use a custom API to build the content: loop through the Contacts related to the Account and for each Contact get and display the Meetings that that contact is a participant of.

You can choose to organize/group the data by Meeting (date, list of participants) or by Contact (which may duplicate meetings if more than one person from this Account attended). I would probably choose the latter and allow the user to filter by date so you don't pull in years of historical data that may not be so relevant.

Keep in mind that the dashlets load regardless of whether your Intelligence Pane is open (I wish they would pull only when that particular dashboard is opened), so the loading of the record could be somewhat slower depending on how you build the dashlet, how much data you pull in etc...

By pulling this data into a Dashlet you can also make sure that it's loaded only for those people who really want/need to see it. Others will simply not add that dashlet to their view.

I'll be interested in seeing the solution you come up with.

FrancescaS

Hello Francesca 

I'm working within the same company with Damien, as he already told we though about some kind of solutions to answer this need.

The first one is about creating a custom API that will loop through the contacts / opportunities (and other objects) that are related to a customer, and address them in a custom subpanel that is easy to build, readonly view as we will only display the information. The only thing we can add will be the order on the columns.

The second thing and the one that is more tricky is to add hooks that will monitor when a meeting is added to a contact, retrieve the customer if exists and add a link between the customer and the meeting. We have to do this job on every cases (modify relationship, delete relationship), and on several modules (contacts, opportunities, etc ...). This will be annoying and very hard to maintain. We proposed the first solution to our customer.

Yours will be fine too, the advantage is that a person that don't want this dashlet didn't add to his dashboard.

Any other point of view will be good to hear :-)

Best regards,

Enes

Hi Francesca,

That was one of our ideas too. 

The drawback of dashlets is that they are not visible in the mobile application AFAIK. It's also a deviation from the standard usability of the app. 

We should petition the editor to include that feature as standard, altough in some of our cases the contact-account relationship is enriched (contact role). 

Thanks for the suggestions, Francesca. These are interesting approaches, but they do not take into account the point of the app. Unfortunately, the suggestion for improvement came from a department that also needs to display this information on an app basis. We have now rejected the request from our colleagues for the time being and hope for further development in the SugarCRM standard. In any case, I will submit this again as an enhancement request.