Absolutely correct, the Related List Query allows multiple conditions to be applied on the related / “joined” table. Still, the “join” can only be done on the sys_id field on the base table, so only tables can be used as related / “joined” table which will have a field containing the sys_id of the base record.
I would thereby also assume that the performance is quite similar to JOIN Query.

Achim, I don’t really have any insight around performance implications between the two approaches….in fact, I had never seen the Related List Query syntax for encoded queries before. Thanks for pointing that out! One thing that does hit me as a difference is that the RLQUERY approach seems to allow for multiple filters to be applied on the ‘joined’ table. The ‘JOIN’ approach did only allow 1 filtering attribute. I’m guessing that the performance is fairly similar between the two as I’m guessing they are both essentially sub queries.

Do you also have insights into any (performance) implications for scenarios in which also a Related List Query can be used similar to JOIN Query?

In the given example of this blog article this could be:

var query = “active=false^RLQUERYincident.problem_id,>=1^active=true^ENDRLQUERY”
var ProbGr = new GlideRecord(‘problem’);
ProbGr.addEncodedQuery(query);
ProbGr.query();

Would be interesting to know if there are any advantages or disadvantages of choosing one possible solution over the other.

Sam, Excellent! I noticed the same in the doc as well…after the article was written. Might be worth a “part 2” and some point. Thanks for linking the doc in!