GlideRecord Query Helper

[shivamvish160]

PR Description:

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
• 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

[WillemZeiler]

Thank you for your submission. In general I would be careful with script includes that wrap the ootb GlideRecord. The syntax is deviating to what every ServiceNow developer knows, it requires additional code execution, and the default functions are not available in the wrapper (f.e. updating a record).

[WillemZeiler]

What is your reason to handle the error in this way?

[WillemZeiler]

I would expect error handling here as well. If an object value is now empty it will query on empty resulting in unexpected behavior that will be difficult to spot.

[WillemZeiler]

If you want to go the wrapper route, it would make sense to add additional error handling, security, and input validations to make it more robust.

[WillemZeiler]

What if, based on the GlideRecord we did, we want to update one or multiple values on the record?

[WillemZeiler]

Thank you for your submission. I have added comments to the code. I would suggest not using wrapper functions like this, but if you want to continue with the code, you can use the comments.
I will close the PR.