Use PDIs? Take our 5-minute survey to help shape the PDI roadmap.

(ServiceNow Administration Fundamentals On Demand) Lab 4.2 - u_cmdb_ci_hardware_hhd

SandroA
Tera Contributor

Hi! 
I was going on lab 4.2 and on Section 5 it tells me to filter the list of rules and find the four u_cmdb_ci_hardware_hhd rules.

Although, I've been back and forth and been sticking with the lab instructions, it does not show such records.

What am I missing?

Thanks!

3 REPLIES 3

SandroA
Tera Contributor

SandroA_0-1730205002379.png

 

PetjaO
Kilo Contributor

This is excactly my problem surely someone will help with this soon

medgington
Mega Contributor
Hi Sandro, 

I realize I'm fashionably late to this party by a couple of years, but since this thread is a top search result for the SNAF Lab 4.2 glitch, I wanted to drop the definitive fix for anyone else who gets stuck here!

If you ever see the "Table name is already in use" error but the four ACL rules refuse to populate in your list view, your Personal Developer Instance (PDI) is experiencing a common metadata sync glitch. The backend database built your records from the previous lab, but the UI cache hasn't indexed them yet.

You can fix this instantly by forcing a cache flush:
 
Step 1: Flush the Instance Cache
  1. Go to your main Application Navigator search bar on the top left.
  2. Type exactly: cache.do and press Enter.
  3. Wait a few seconds for the page to process. A white screen will load confirming the cache purge is complete. This safely forces the instance to rebuild its schema map and sync the backend database with the UI.
Step 2: Search via Wildcard
  1. Navigate back to All > System Security > Access Control (ACL).
  2. In the search bar for the Name column, use an asterisk wildcard: *u_cmdb_ci_hardware_hhd and press Enter.
Once the cache resets, the indexing fix becomes permanent. You can then clear your search bar and use the standard filter builder (Name contains u_cmdb_ci_hardware_hhd) without any wildcards, and all four default CRUD rules will populate perfectly.

Hopefully, this helps future developers saving their sanity on Lab 4.2!