simplified

[ChaseMillers]

PR Description:

Previous script, now refactored:

Manual parent table traversal and sys_dictionary queries are replaced with ServiceNow’s built-in [GlideRecord.getElements()] for listing all fields.

Field existence checks now use [GlideRecord.isValidField(fieldName)].

Table ancestors are printed using [SNC.TableEditor.getTableAncestors()] if available.

test:

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• 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

[Atul-LNG]

Please add the Readme file as well.

[ChaseMillers]

This was just a simplification of a script. It already has a README

[Atul-LNG]

README must be a separate file @ChaseMillers as per guidelines.

[ChaseMillers]

There IS a separate REAME file to this folder. You don't want two of them.

This is based off a script that was already made. It was made by me.
After making it I later realized some functionality improvements/simplifications and added them in.

[mskoddow]

@Atul-LNG
This PR is not a complete new one but an update to the already merged PR #2497 (@ChaseMillers please provide such PR references as this helps us a lot to understand the history)
Therefore, in the main branch the readme is already existing: https://github.com/ServiceNowDevProgram/code-snippets/tree/main/Specialized%20Areas/Predictive%20Intelligence/Training%20Data%20Preparer/Incident%20Table

[ChaseMillers]

@Atul-LNG This PR is not a complete new one but an update to the already merged PR #2497 (@ChaseMillers please provide such PR references as this helps us a lot to understand the history) Therefore, in the main branch the readme is already existing: https://github.com/ServiceNowDevProgram/code-snippets/tree/main/Specialized%20Areas/Predictive%20Intelligence/Training%20Data%20Preparer/Incident%20Table

I'll be sure to include the PR references next time. Thanks!