Has anyone else noticed that when you save a service request for the first time, the createddatetime field gets updated to the current time (not the date/time displayed when you clicked on the new button), even if you spent some number of minutes authoring the new request.
From what I can tell, it seems to run the initialization rules twice, once when you click on the new button, and then again when you save it. This is a different behavior when compared to Incident or Email. Those objects seem to retain the createddatetime field value when you click on new and then save.
I am using 2016.2.1 on premise. Does anyone know of a workaround? I contacted support and they suggested adding an if to the initialization rule and only set it to currentdatetime when it is null. But that did not work.