Creating a field to track next steps on an opportunity

Hi Ada Napierala,

With regards to option 2, have you considered using the Comment Log field for this purpose? It's not clear from your description if the comment log feature where past entries are uneditable would be a benefit or a hindrance, but it does provide the ability to enter timestamped records so the entire history of 'next steps' would be visible.

With regards to the first option, if your main purpose is so that users viewing the opportunity know when it was last changed by someone, we have a plug-in, Upsert Last Modified By, that cleanly displays who and when the field was last changed.

Chris

Hi Chris Raffle

What do you mean by comment log field? I am only aware of Comment Log in as a dashlet, and I skeptical on using this because it's not reportable. 

For the plug-in, it's interesting, I will explore it - thanks :) 

Hi Ada Napierala,

The Comment Log feature can be added to the record view layout of modules or used via the dashlet. If you go to the module's record view layout in Studio, you should see Comment Log as an available field to add if you do not already have it on the layout.

If reporting is a primary need for this use case, then André's solution is likely the most appropriate. Both the comment log feature and our Upsert Last Modified By plug-in leverage backend data that are not accessible through the standard reporting features. You could leverage Advanced Reports to get desired data from either of those solutions. Advanced Reports requires a foundational knowledge of Sugar's database structure for storing the appropriate data and writing database queries to target that data. 

Hi Ada Napierala,

The Comment Log feature can be added to the record view layout of modules or used via the dashlet. If you go to the module's record view layout in Studio, you should see Comment Log as an available field to add if you do not already have it on the layout.

If reporting is a primary need for this use case, then André's solution is likely the most appropriate. Both the comment log feature and our Upsert Last Modified By plug-in leverage backend data that are not accessible through the standard reporting features. You could leverage Advanced Reports to get desired data from either of those solutions. Advanced Reports requires a foundational knowledge of Sugar's database structure for storing the appropriate data and writing database queries to target that data. 

Hi Chris Raffle

The comment log on the layout looks really good, however yes I do need to be able to create summaries of comment logs per opportunity. 

For Sugar database structure - could you please recommend documentation to learn more about it?

Hi Ada Napierala,

The schema for each version of Sugar is linked from the support site under their 'Product Guides' section:

https://support.sugarcrm.com/Documentation/?docVersion=12.2&docEdition=Sell

From there, you can learn how tables are related to one another. For the Comment Logs feature, the comments are stored in the commentlogs table and you can see which tables it connects to in the docs:

https://apidocs.sugarcrm.com/schema/12.2.0/ent/tables/commentlog.html

To pull specific comment logs related to an opportunity, you would connect opportunities > commentlog_rel > commentlogs.

Superb, thanks! 

The comment log field maybe have a lot of comments - is it possible to collapse the comments? 

You cannot collapse the field itself. Sugar has an enhancement request (81830) tracking this requirement. I recommend opening a support case with Sugar referencing that enhancement to help them weigh customer impact.

Your options to avoid excessive scrolling when there are a lot of comment log entries are:

1. Place the field in its own panel on the record view layout. Panels can be expanded and collapsed by users.
2. Use the Comment Log dashlet instead of the record view field.