How to populate a newly created field for older created tickets.

[Niletor]

Hi guy's, Recently I have created a new entry in the table for Requests/tickets which shows for what purpose this Ticket was raised for, the newly created entry was already there in the record producer but there was no entry created in database level or table level , so after creating the new entry in the table and mapping it from intake level to table the new field is getting populated for new requests but not for older requests. How should I make this field populated for older requests .

[Ravi Gaurav]

Hi @Niletor 

For already existing field if you need to update all together better go with Fix Script.

Glide to the table add Query to it to whatever record you wanted to update and then run the script.

Below is just Sample (and it will update all record so choose your field wisely):-

var inc = new GlideRecord('incident');

inc.addEncodedQuery('category=software');

inc.query();

gs.print(inc.getRowCount());

while (inc.next()) {

    inc.short_description="Test"

    inc.update()

}

[Niletor]

Thanks Ravi, but it is not working for more clarity this-
I have newly created an entry/field in the table for which purpose the request is raised, name-"tgov_purpose" .this field gets populated from the intake/record producer level with question name -"what_purpose". After creation whatever value we are putting in intake form for "what_purpose" ,the field for "tgov_purpose" also gets filled for new records but not for older records, How can I make this "tgov_purpose" populated for previously created Records/Requests

[Ravi Gaurav]

Hi @Niletor 
I agree with @Dr Atul G- LNG if the count is Less then you can update at one go together as shown in the figure below :-
Press shift downward arrow and double click the first cell

or Use the Backgrounnd script (Not a best practice) or Fix Script (Best Practice)

// Query the table where you want to update records
var gr = new GlideRecord('your_table_name'); // Replace with your table name
gr.addQuery('tgov_purpose', ''); // To find records where tgov_purpose is empty (optional)
gr.query();

while (gr.next()) {
// Get the value from the intake/record producer form's field
var whatPurpose = gr.what_purpose; // Adjust based on how you store or access this data

// Set the value to the new field
gr.tgov_purpose = whatPurpose;

// Update the record
gr.update();
}

[Dr Atul G- LNG]

Hi @Niletor 

It depends on what type of field it is. Usually, we avoid populating new fields for old records, it can impact reporting / SLA as well and also in this case the value will be the same for all old records.