Hey,
When posting code on the community, it'll be easier for us to read if you wrap the content in a code sampe (image below)
In regards to your issue, a couple code-smells to tidy up to avoid possible collisions:
- Try to avoid using "gr" as a variable name. Variables are global and it's more than likely that SN have used "gr" to store a value which you could overwrite
- Use getters and setters rather than directly assigning a value. Although SN tries to be helpful and understand your intent, it can lead you to running into some unexpected behaviour
- When setting date/time field values, you either need to to set it using the system date/time format or the users (the latter requiring the use of setDisplayValue() rather than setValue())
(function() {
var table = $sp.getParameter('table')
var sys_id = $sp.getParameter('sys_id')
var currentRecordcurrentRecordGR = new GlideRecord(table);
if (currentRecordGR.get(sys_id)) {
data.displayValue = currentRecordGR.getDisplayValue('u_colleagues_leaving_date_and_time');
data.value = currentRecordGR.getValue('u_colleagues_leaving_date_and_time');
}
if (input && input.action) {
var action = input.action;
if (action == 'updatedate') {
currentRecordGR.setValue('u_colleagues_leaving_date_and_time' , input.updatedate);
currentRecordGR.setValue('u_uipath_comment' , "script ran");
currentRecordGR.update();
gs.addInfoMessage("Leave Date updated ");
}
}
})();Change your usage of the spDatePicker directive to directly bind the value such as
<sp-date-picker ng-model="data.u_colleagues_leaving_date_and_time" sn-include-time="true"></sp-date-picker>
