Idea Description

Currently, when a customer address is edited or updated in Dynamics 365, the system saves the modified address as a completely new address line in the backend, instead of updating the existing record. This means that for every small change (e.g., correcting a street name or postal code), a new address is stored.

Over time, this results in accounts having dozens of duplicate or slightly modified addresses. This creates multiple issues, including:

• Customer account statements failing or timing out, as the system flags these as long-running accounts due to excessive address records.
• Data bloat, making account management unnecessarily complex.
• Confusion for end users, since they cannot easily identify the "true" current address.

Suggested Solution:

Introduce an option or system logic to allow in-place updates of an existing address line, rather than always saving a new one. For audit/history purposes, changes could still be tracked (e.g., via change logs or version history), but the customer’s account should not accumulate redundant address records.

This would improve performance, prevent statement generation errors, and simplify account management.