The CreatorCon Call for Content is officially open! Get started here.

Company search results with no results

Piemur1
Tera Contributor

I'm playing around in my personal dev instance on a freshly blanked out instance with no dummy data. So I was creating some test dummy records and I've begun to notice that despite me creating a company for me to create hardware records out of, when I created a new asset record, the search for Company doesn't come back with any results.

Piemur1_0-1727901258180.png

I've created several Company records so I don't understand why this is showing up blank

Piemur1_1-1727901320108.png

If anyone can give me any advice I would greatly appreciate it. If you need anything further from me, just let me know!

1 ACCEPTED SOLUTION

As much as I love the ServiceNow platform, this is one of many little quirks that peeve me off to no end.  That Reference Qualifier makes absolutely no sense.  I don't know for sure, but it was probably configured that way based on the OOTB data, which is is terrible.

 

It should be something like "manufacturer=true^ORvendor=true" instead.  You could create a Dictionary Override on the "cmdb.company" field that would fix it for all CMDB tables without messing with the Reference Qualifier on the base table which would in turn mess up all the "company" fields on the child CMDB tables.

View solution in original post

12 REPLIES 12

Oh, no worries about that. I only modified it on my personal developer instance. I'm trying to run some scenarios for our upcoming system and was curious why the companies weren't showing up when I was creating test dummy records in my PDI.

How could I apply the override on the whole "cmdb_ci" table? I'm looking at the create reference override for "cmdb_ci" on the "company" column, but it requires me to select a table. Or is it because I'm on the "cmdb_ci" table and I should be putting the override on the base table "cmdb" and put "cmdb_ci" as the table in that selection field?

Piemur1_0-1729012778784.png

Sorry for so many questions, I just want to figure out a correct method for when we actually start doing this with live data.

No problem, this is how we learn.

 

Overrides are applied on the lower (or higher, never really sure how to describe it) table.  So in this case, if you want an override for the "cmdb_ci" table, you need to navigate down to it's parent, "cmdb", and create the override there.  If you do that, you will see the "cmdb_ci" table listed in the drop-down list.  So that override will take precedence over the hierarchy until another is added, if required.

 

JimCoyne_1-1729201590120.png

 

If ServiceNow ever "fixes" the Reference Qualifier on the "cmdb" table, you could then remove the override and all tables would use that new qualifier.  It's just a pain fixing the Reference Qualifier on the "Company" field itself because of all the Skipped Records that will be generated in the future during upgrades/updates.