Location Field in Discovery Job

BK14
Mega Guru

Good day experts,

When I click the magnifier in front of the Location field in a discovery jobs (lookup using list), it displays the locations that are not active (Active = False). Is there a setting to change this behavior and to show only the active locations to pick?

 

BK14_0-1736535362521.png

 

3 REPLIES 3

AndersBGS
Tera Patron
Tera Patron

Hi @BK14 ,

Have you looked at the reference qualifier for the mentioned field?

If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.

Best regards
Anders

Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/

Najmuddin Mohd
Mega Sage

Hi @BK14 ,

Actually there is no field on Location (cmn_location) table to tell whether it Active or not.

So, create a custom field and utilise to use only Active(Custom field) = true in the reference qualifier using Configure dictionary.


you can check the below thread: 
https://www.servicenow.com/community/itsm-forum/make-location-inactive/td-p/467851#:~:text=Create%20....

NajmuddinMohd_0-1736586051277.png


NajmuddinMohd_1-1736586392970.png



If the above information helps you, Kindly mark it as Helpful and Accept the solution.
Regards,
Najmuddin.

BK14
Mega Guru

Thank you both for the information. The reference qualifier was not set to anything. The field that shows the status of the Location is called "Active". 

I think there is an issue with the location qualifier. 

  • If it is not set for anything (which was the case for us) it should show all locations, but it was only showing those that Active == False.
  • If I set the Active == True in the qualifier, it shows the active locations that don't have Parents (Parent == Empty)
  • If I set Active == True && Parent Is Not Empty, then I get the active ones that have Parents. 
  • If I set Active == True && Parent Is Anything, I still get the ones that have parents.

So I am confused how this filter works. Do you guys see the same issue?

By the way, when I set the filter, it impacted the performance of our instance. I think that is why someone had removed the filters from the reference qualifier.

 

BK14_0-1736776937647.png