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.

Using ^JOIN in encoded query

Mathias Johans1
Mega Expert

Hi!

I have recently bumped in to an unusual encoded query that I need to adjust.

The goal is to query incidents where there are breached Task SLA's, where Task SLA.stage is not cancelled.

In the script include "SOWUpcomingLinkProvider_Incidents", I can find the syntax "^JOINincident.sys_id=task_sla.task!has_breached=false". This is then run on a GlideRecord Query on incident table. I suspect that I need to add the "stage!=cancelled" query, but it seems that this syntax does not work like a normal query.

i have tried "^JOINincident.sys_id=task_sla.task!has_breached=false^stage!=cancelled", but this seems to be wrong.

Can someone help me clarify this?

1 ACCEPTED SOLUTION

Thanks for your help!

I was looking some more at the code and realized that I should add the full ^JOIN syntax once more to get the desired outcome; eg: '^JOINincident.sys_id=task_sla.task!has_breached=true' + '^JOINincident.sys_id=task_sla.task!stage!=cancelled';

You did point me in the right direction, so it was very helpful!

View solution in original post

10 REPLIES 10

Sebastian L
Mega Sage

Hi Mathias,

It is a Join Query, so you need to add the "!" syntax to add an additional condition.

 

So it could look something like this: 

"^JOINincident.sys_id=task_sla.task!has_breached=false!stage!=cancelled" 


Best regards,
Sebastian Laursen

Hi,

Unfortunately, that doesn't work either.. even if I try another condition, eg "^JOINincident.sys_id=task_sla.task!has_breached=false!stage=completed", I still get Cancelled Task SLAs 

And it is not because there already are Task SLAs exisiting for the incident? So if the incident has 3 SLAs, and one of them is cancelled, then it will still return the incident since it is a join, and are looking for any condition that matches in task_sla table with that task(incident).. Just wondering 🙂 

 


Best regards,
Sebastian Laursen

I wish it was that simple.. The Incident that keeps showing up has 2 Task SLA's, both are cancelled..