Clone Parent Records into Child

[SumithThota]

PR Description:

Copies records from a parent table into a child table in ServiceNow, optionally preserving the parent sys_id as a reference on the child.

Purpose

Provide a simple example that shows how to iterate parent records (GlideRecord), map selected fields, create child records, and optionally keep a parent reference, useful as a Scripts - Background snippet or a starting point for a Script Include / scheduled job.

Behavior (high level)

• Runs immediately (IIFE).
• Queries the parent table x_parent_table using addQuery('your Query') and query()
• For each matching parent record:
• Initializes a new child record on the child table x_child_table.
• Copies example fields short_description, description from parent to child.
• Sets childGR.parent = parentGR.sys_id to retain a link to the parent.
• Inserts the child record.
• Logs completion with gs.info().

Contract (inputs / outputs)

Inputs:

1. parent table name (string in the script)
2. query/filter addQuery or encoded query
3. child table name (string in the script)
4. hard-coded field mappings inside the script

Outputs:

1. New records inserted into the child table
2. System log entry via gs.info()

Proof

I have attached a screenshot which shows a child table (u_child_Incs) having copies Parent table (incident) records.
Please do check it once

Pull Request Checklist

Overview

• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[mskoddow]

Thanks for your contribution! However, I don't see the added value of such a script. It's the opposite of what we want to design in ServiceNow. A data scheme with the least redundant data. Please provide a real-world use case for such a scenario to clarify its purpose!

[mskoddow]

@SumithThota
Please finish the requested changes by the end of today. Otherwise, I'll close that pull request.

[mskoddow]

@SumithThota
Due to missing changes, I have requested before, I'm gonna close that PR. Feel free to open another one.