Skip to main content

Incident form: client scripts are displaying "A new record with this value will be created automatically" messages everywhere. Why???

Anyone spotted the "A new record with this value will be created automatically" messages displayed all over the incident form as per the attached screenshot?

Anyway, I thought I'd share the explanation provided by ServiceNow...

Solution proposed by  (NOW)

Hello Ruen,

We are placing this incident in Solution Proposed.

Reason: I have located documentation that will provide insight on what is happening.

Issue: A new record with this value will be created automatically is showing under an empty reference field

Solution Proposed:
According to the documentation for reference field type :

https://docs.servicenow.com/bundle/jakarta-servicenow-platform/page/administer/field-administration/concept/c_ReferenceField.html?title=Reference_Fields#Enabling_Dynamic_Creation

Enable dynamic creation : When dynamic creation is enabled, entering a nonexistent value in a reference field creates a new record on the referenced table instead of returning an error.

This means that this is enabled on the instance.

Please let me know if the approach above has resolved the issue for which this Incident was raised.

Best regards,
ServiceNow



Comments

Popular posts from this blog

Get URL Parameter - server side script (portal or classic UI)

Classic UI : var sURL_editparam = gs . action . getGlideURI (). getMap (). get ( ' sysparm_aparameter ' ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); } Portal : var sURL_editparam = $sp . getParameter ( " sysparm_aparameter " ); if ( sURL_editparam == 'true' ) { gs . addInfoMessage ( 'parameter passed ); }

ServiceNow check for null or nil or empty (or not)

Haven't tested these all recently within global/local scopes, so feel free to have a play! option 1 use an encoded query embedded in the GlideRecord , e.g.  var grProf = new GlideRecord ( 'x_cls_clear_skye_i_profile' ); grProf . addQuery ( 'status=1^ owner=NULL ' ); grProf . query (); even better use the glideRecord  addNotNullQuery or addNullQuery option 2 JSUtil.nil / notNil (this might be the most powerful. See this link ) example: if ( current . operation () == 'insert' && JSUtil . notNil ( current . parent ) && ! current . work_effort . nil ())  option 3 there might be times when you need to get inside the GlideRecord and perform the check there, for example if the code goes down 2 optional routes depending on null / not null can use gs.nil : var grAppr = new GlideRecord ( 'sysapproval_approver' ); var grUser = new GlideRecord ( 'sys_user' ); if ( grUser . get ( 'sys_id' , current . approver )){