Why Comments Cannot Function as Primary Module
The CRM requires users to define a single primary module and up to two submodules when building reports. Comments are linked distinctly to individual modules (Leads, Opportunities, Accounts, etc.), so selecting 'Comments' as a standalone primary module yields no data because comments cannot exist independently of their parent module.
Comments require a defined primary module context to generate results, as they are always attached to specific records within other modules.
How to Track Comments Across Multiple Modules
To create reports showing comments from different modules, you need to build separate targeted reports for each module where comments exist:
Comments Created Today - Leads: Set Leads as primary module and filter for today's comments
Comments Created Today - Opportunities: Set Opportunities as primary module and filter for today's comments
Comments Created Today - Accounts: Set Accounts as primary module and filter for today's comments
Each report will show comment activity specific to that module, providing comprehensive coverage of all comment activity across your CRM.
Best Practices for Comment Reporting
💡 Tip: Create a dashboard that displays multiple comment reports side-by-side to get a comprehensive view of all comment activity across modules.
✅ Best Practice: Use consistent naming conventions for your comment reports to make them easy to identify and organize on dashboards.
⚠️ Note: While Comments appear in the primary module dropdown, this is a known limitation. The development team is aware of this configuration issue.
