Title:

Improve ModifiedDateTime Behavior for Main Account Form Updates in Dynamics 365 Finance

Problem Statement:

When users update fields in the Main Account form, the ModifiedDateTime in the MainAccount table does not change if the updated field belongs to a related table (e.g., DimensionAttributeValue).

This creates confusion because:

• The UI initially shows ModifiedDateTime updated after saving.
• After refreshing the form, ModifiedDateTime reverts, making users think the update was lost.

Current Behavior:

• Fields in MainAccount → ModifiedDateTime updates in MainAccount.
• Fields in DimensionAttributeValue → ModifiedDateTime updates only in DimensionAttributeValue, not in MainAccount.

Impact:

• Users expect ModifiedDateTime in MainAccount to reflect any changes made in the Main Account form.
• The discrepancy between UI and database behavior leads to misunderstanding and unnecessary troubleshooting.

Suggested Improvement:

• Option 1: Update ModifiedDateTime in MainAccount whenever any field in the Main Account form is changed, regardless of the underlying table.
• Option 2: Display a clear indicator in the UI showing which table the update applies to (e.g., “Last modified in DimensionAttributeValue”).
• Option 3: Provide a consolidated ModifiedDateTime that reflects changes across all related tables for better transparency.

Benefits:

• Improves user experience and trust in the system.
• Reduces confusion and support cases related to perceived data inconsistencies.
• Aligns UI behavior with user expectations for audit and compliance tracking.