Skip to main content

known issue with inherited role removal

 below script can be used as a workaround to tidy up inherited roles which can't be removed which is being caused by the inherited flag being set to true on sys_user_has_role

var grUser=new GlideRecord('sys_user'); if (grUser.get('sys_id', '539be781dbfc5010dde5d8c2f39xxxxx')){ gs.print(; var grGrpMem=new GlideRecord('sys_user_has_role'); grGrpMem.addQuery('user', grUser.sys_id); grGrpMem.addQuery('inherited', true); grGrpMem.query(); gs.print(grGrpMem.getRowCount()); while ({ //grGrpMem.autoSysFields(false);//--leave last updated intact //grGrpMem.setWorkflow(false); grGrpMem.inherited= false; grGrpMem.update(); gs.print(grGrpMem.sys_id); grGrpMem.deleteRecord(); } }


Popular posts from this blog

URL link in addInfoMessage

var ga=new GlideAjax('gld_HR_ajax'); ga.addParam('sysparm_name', 'checkEmployeeNumber_hrProfile'); ga.addParam('sysparm_hrprofilenumber', g_form.getValue('number')); ga.addParam('sysparm_employeenumber', newValue); ga.getXMLAnswer(function(answer) { if (answer!='undefined' && answer!=''){ var navURL="<a style='text-decoration:underline;color:blue'" + answer + ">" + answer + "</a><img width='3' src='images/s.gif'/>"; var sMsg='The employee number entered already exists on another HR Profile ' + navURL; //alert(sMsg); g_form.showErrorBox('employee_number', 'error - please check'); g_form.addInfoMessage(sMsg); } });

GlideRecord setValue

setValue(String name, Object value) Sets the specified field to the specified value. Normally a script would do a direct assignment, for example,  gr.category = value . However, if in a script the element name is a variable, then  gr.setValue(elementName, value)  can be used. When setting a value, ensure the data type of the field matches the data type of the value you enter. This method cannot be used on journal fields. If the value parameter is null, the record is not updated, and an error is not thrown!/api_doc?v=madrid&id=r_GlideRecord-setValue_String_Object