When a user submits a marketing form with data that already matches an existing record in Dataverse (e.g., identical first name, last name, and email), the platform currently triggers OnChange events and downstream processes (such as plugins and Power Automate flows), even though no actual data has changed. This behavior leads to unnecessary processing, confusion in audit trails, and potential performance overhead. This was confirmed to happen at least with emailaddress1 field with Microsoft Support.

I suggest Microsoft to introduce a mechanism to detect and suppress redundant OnChange triggers when submitted data from marketing form is identical to existing values. This would improve system efficiency, reduce capacity use in automated logics, and align the event model more closely with actual data changes.