How to add mappings to name value pairs field

[Joe83]

Hi ServiceNow Community Developers,

I am using a name value par field for the first time and I am trying to populate the name and value using the script that ServiceNow provided as an example here

https://docs.servicenow.com/bundle/paris-platform-administration/page/administer/field-administratio...

I am however running into an issue and I am not sure what is it that I am doing wrong. There are things that I am noticing that don’t look right to me with the provided script that I am using as my model here. The provided script has the initialize() function which to me says that we are going to create a record somewhere however I don’t see the insert() function in the provided script. I am not sure if I am missing something but would you please take a look ad advise.

Here is my script https://ven03962.service-now.com/nav_to.do?uri=sys_script_client.do?sys_id=5f7f41e21b0060102d0f99ba2... and it’s a very simple copy of the one the vendor provided above. It runs on loading of a change record.

Thanks,

John

[Ankur Bawiskar]

Hi,

please share your script here

Regards
Ankur

[Joe83]

Hi Ankur,

Sorry about that, here is my script

Thanks,

Johannes

[Ankur Bawiskar]

Hi,

name-value pair field stores value in json format

1) GlideRecord is not recommended in client script

But just for your understanding your script should look like this

var gr = new GlideRecord('change_request');

gr.initialize();

var jsonObj = {

"name1":"value1";

"name2":"value2"

};

gr.u_xlr_variable = JSON.stringify(jsonObj);

gr.insert();

Regards
Ankur

[Michael Jones -]

So, name/value pairs are simply part of any javascript object. This example shows how you can add new name/value pairs to an object and later access those values. The reason they are using gr.initialize() is to instantiate the object. You are correct, they are not actually creating a record in this case, which is why they don't call gr.insert(); all of the data lives, and dies, within the scope of the script and is never written to the database. 

I'm not able to access your example, so I'm not entirely sure what you're trying to accomplish but, in essence you can use this type of functionality to "tack on" additional values to an existing object while that object exists in your script (perhaps to hold some temporary values or calculated values) but once your script ends that data will be lost. The only way to save that data would be to write it to fields that exist on the record being created, for example, and those would need to already exist; this would not let you create fields on the fly. 

This is, basically, how dot-walking works. The values of the fields are written to the object using name/value pairs, which you can then access. That's why, one a business rule for incident, you can get the number with current.number. Current is the object, number is name, and the actual number is the value. 

In the same vein, if you were in a business rule and used a line like current.number.myvalue = 'Hello'; then later any call to current.number.myvalue would return "Hello" - while that object exists in memory. 

Hope this helps!

If this was helpful or correct, please be kind and click appropriately!

Michael Jones - Proud member of the CloudPires Team!