Hello @SeemaJenitT
query() vs. _query()
query(): This is the standard and most commonly used method to execute a GlideRecord query. After setting up your filters (e.g., using addQuery(), addEncodedQuery()), you call gr.query() to fetch the matching records from the database.
var gr = new GlideRecord('incident');
gr.addQuery('active', true);
gr.query(); // Executes the query
while (gr.next()) {
gs.print(gr.number);
}
_query(): This method provides the same functionality as query(). However, it's specifically intended to be used in rare scenarios where the table you are querying has a column (field) named query. If such a field exists, using gr.query() might lead to unexpected behavior or errors because query could be interpreted as the column name rather than the method. Using _query() resolves this ambiguity.
// Example: If 'my_custom_table' has a field named 'query'
var gr = new GlideRecord('my_custom_table');
gr.addQuery('state', 'open');
gr._query(); // Use _query() to avoid conflict with a 'query' field
while (gr._next()) { // Often used with _next() for consistency
gs.print(gr.name);
}
next() vs. _next()
next(): This is the standard and most commonly used method to move the GlideRecord cursor to the next record in the result set. It returns true if there is a next record and moves to it, and false if there are no more records. It's almost always used within a while loop to iterate through all records returned by a query.
var gr = new GlideRecord('incident');
gr.query();
while (gr.next()) { // Moves to the next record and checks if it exists
gs.print(gr.short_description);
}
_next(): Similar to _query(), this method provides the same functionality as next(). It's used in specific cases where the table you are iterating through has a column (field) named next. Using gr._next() prevents potential conflicts or misinterpretations with a field named next.
// Example: If 'another_custom_table' has a field named 'next'
var gr = new GlideRecord('another_custom_table');
gr.query();
while (gr._next()) { // Use _next() to avoid conflict with a 'next' field
gs.print(gr.display_value);
}
If my response was helpful, please mark it as correct and helpful.
Thank you.
