Hi,
Only noticed this while comparing unmanaged layer to last managed (msdyn_SwarmingForCS in this instance), it's a Sandbox environment with only Sales Ent installed. Using the new UI, all I did was add a single field into a Main form and this bunch of XML seems to get removed...
<event name="onchange" application="true" active="true" attribute="contractid">
<InternalHandlers>
<Handler functionName="Mscrm.contractid_onchange" libraryName="Service/Incident/Incident_main_system_library.js" handlerUniqueId="1ff26f3d-f9f4-470b-a379-bc74ce466a53" enabled="true">
<dependencies>
<dependency id="contractdetailid"/>
</dependencies>
</Handler>
</InternalHandlers>
</event>
<event name="onchange" application="true" active="true" attribute="contractdetailid">
<InternalHandlers>
<Handler functionName="Mscrm.contractdetailid_onchange" libraryName="Service/Incident/Incident_main_system_library.js" handlerUniqueId="fde679b3-af20-4b24-ab99-13f7de54fbb1" enabled="true">
<dependencies>
<dependency id="contractid"/>
</dependencies>
</Handler>
</InternalHandlers>
</event>
Doing the same on the Classic UI doesn't.
I tested across another Sandbox with Customer Service installed and same thing happened. Not sure if it's by design but seemed a bit odd to just remove a bunch of events that I didn't even tough??!!?!
Mark
Only noticed in the XML when using the Compare feature. At a guess it's SLA related as refers to contractid, not using SLAs in that tenant so wouldn't notice anyway.
That is odd. But not a huge shock. There is a considerable difference between how the classic and modern form editors interact with the form XML, and not all the kinks have been worked out. Are you noticing any behavioral difference, or is it only observable in the xml? It is possible that these events are just deprecated functionality that never got perfectly purged...
WarrenBelz
109
Most Valuable Professional
Michael E. Gernaey
82
Super User 2025 Season 1
MS.Ragavendar
72