Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Hierarchical queries not working - Yokohama new features

shun6
Giga Sage

Hi developers,

 

In Yokohama release, new query operation is added called "hierachical queries".

I configured it following docs like below image and executed query but it didn't work.

Is there anyone who can execute hierachical queries successfully?

docs: Building hierarchical queries

shun6_0-1740230750248.png

 

I can't get any result when using hierachical queries although there're records which parent is South America.

shun6_1-1740230831983.pngshun6_2-1740230910690.png

 

Regards,

 

9 REPLIES 9

Kieran Anson
Kilo Patron

Feels like there is a missing business rule/job that should trigger when creating a hierarchy record that adds codes to the target table records. I'd recommend raising a HI case

 

sheryl
Tera Expert

I am experiencing the same issue... if you find the solution, please post back here again!

philsharp
ServiceNow Employee

Greetings! 

I, too, can't get the [is in hierarchy] operator to show up in any condition builders, even after doing my best to follow the instructions for creating the appropriate record in the sys_record_hierarchy table. 

 

There appears to be very little automation built against the table in my build of Yokohama (I'm using an employee instance w/ build tag:  glide-yokohama-12-18-2024__patch1-02-21-2025)—no Business Rules, no Flows, no mention of it in Events or Script Actions or Scheduled Jobs, and a code search from within Studio for the table itself comes up only with the single Client Script and handful of ACLs you'd find using Configure-->All from the table.

 

This is a bit of a bummer since I'd planned to include the functionality in a K25 session I'm hosting. 😅

 

(Update: I've opened a HI case. Let's see!)

shun6
Giga Sage

@sheryl 

@philsharp 

The support team responded, stating that due to internal issues, this feature is disabled by default...

Additionally, they mentioned that enabling this feature is not recommended.