Before You Begin
You should have:
Admin access to your Dazos instance
Understanding of which modules need to share field data
Ability to create custom fields
Understanding Historical Data Field Limitations
Native Historical Data fields in Dazos are hard-coded and designed to update only from their parent module level. For example, the "Last Comment On" field in Accounts will only update when comments are made directly at the Account level, not from related modules like Intake Opportunities.
Important: These core system fields cannot be reconfigured to trigger updates from other modules due to their hard-coded nature.
Steps to Create Cross-Module Field Updates
When you need to track activity across modules, create a custom field specifically designed for cross-module updates:
Identify the limitation: Confirm that the native field is not capturing the data you need from related modules
Create a custom field: Add a new custom field with a descriptive name that indicates its cross-module purpose (e.g., "Last Opp Comment On")
Configure the field logic: Set up the custom field to trigger updates from the source module (e.g., Intake Opportunities)
Test the functionality: Verify that the custom field populates correctly when activity occurs in the source module
Expected Result
After creating the custom field:
The new field will automatically capture and display dates from the specified source module
You will have visibility into cross-module activity for reporting purposes
The native Historical Data field will continue to function as designed for its original module
Common Cross-Module Scenarios
This solution applies to various cross-module tracking needs:
Comment dates from Opportunities to Accounts
Activity timestamps from sub-modules to parent records
Status changes that need to be reflected across related modules
Best Practices
💡 Tip: Use clear naming conventions for custom cross-module fields to distinguish them from native fields (e.g., "Last Opp Comment On" vs "Last Comment On").
✅ Best Practice: Test the custom field thoroughly across different scenarios to ensure it captures all relevant activity from the source module.
Related Resources
Creating Custom Fields in Dazos
Understanding Historical Data Fields
Module Relationship Configuration