Mohammad Alsharayri If this only happens in the context of disabling / re-enabling a DateTime field, please create a case so that we can identify the defect.  It would be helpful to put together a simple process app that demonstrates this.  With this, hopefully finding a work around / JS fix will be easy.

I ran into this identical issue a few weeks ago. As a workaround, on the form action where you re-enable the calendar, execute the following javascript:

ttcalpopupobj = new CalendarPopup()

Yes you can try it, disable and re-enable a date\time field using a form action,

Thank you, that line didn't work for me. I did a workaround using javascript to hide/show the date-Icon:

To hide it:

var dateIcon = document.getElementById(GetFieldByName("DateTime Field Name").id+'cal');
dateIcon.style.display = 'none';

and to show it again in another form action I wrote this:

var dateIcon = document.getElementById(GetFieldByName("DateTime Field Name").id+'cal');
dateIcon.style.display = 'inline';


and to prevent the user from changing the value manually I made the field read-only instead of disabling it as the whole issue is with disabling the field, using this code:

const DateFieldInput = document.getElementById(GetFieldByName("DateTime Field Name").id);
DateFieldInput .setAttribute('readonly', true);

and it is working fine with me.

Mohammad Alsharayri   To confirm, what version are you currently running?

11.4.2 Build 8

So it has been an issue for a while.  We identified it in 11.7.1 and 11.8.  My tests in 12.2 show that is fixed.

It looks like that, good to know that it is fixed now in the new versions.