setDisplayValue not working in scoped app

[Sue Frost]

I have a piece of code copied from a global app to a scoped app and the "setDisplayValue()" command isn't working as expected. I don't see any documentation that suggests that the behaviour of "setDisplayValue()" is different in a scoped app.

Here's my code:

//4) as a last resort, get the default email from the property
if(intakeGroup == ''){
	gs.info("Prioritization and Routing Check - Default");
	intakeGroup = gs.getProperty('x_enig_commcase.commercial.processing');
}

...

/* If the Current User is Web Service and the Case Status is currently not Response Received nor On Hold */
if(isWebService && current.state!='12' && current.state!='11'){

//If no matching Records on the Priorization Matrix
if(!validGA || !validPrioritization){
								
	gs.info("Prioritization and Routing Check -  Point 99");
	current.assigned_to = '';
	//current.assignment_group = intakeGroup;
	current.assignment_group.setDisplayValue(intakeGroup);
	current.state = '1';
	current.u_sla = '';
	return;
}
}

If I store the SYSID of the group in the property, then the assignment group is set correctly.

If I store the NAME of the group, then the assignment group is NOT set.

The original code stores the NAME. I'd much prefer to keep it as is because otherwise I'll have to see where else that property is referenced and make other updates.

Does anyone know why this isn't working?

[Mark Roethof]

Hi there,

Interesting. Like Chuck already mentioned, the setDisplayValue like how you are applying should be oke.

Have you debugged if intakeGroup gives you the expected value? I don't see your full script, so don't know. Though you might try adding .toString() for example.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list