Added cmdb_ci table to global search

SaiVasanth · ‎07-13-2023

Hi,

I have followed the below document and I have tried to add the cmdb_ci table to global search. The CIs are showing perfectly in my PDI. However, I have tried the same thing in my client dev instance and it's not showing the CIs there.

https://docs.servicenow.com/bundle/tokyo-platform-administration/page/administer/search-administrati...

Tushar · ‎07-13-2023

Hi Sai,

there could be a few possible reasons for this behavior:

Table Configuration: Check the table configuration of the cmdb_ci table in your client development instance. Ensure that the table is active and searchable. Verify that the necessary fields are present and configured correctly for search indexing.
Indexing Status: Confirm that the global search indexing is up to date in your client development instance. The search indexing process periodically runs in the background to update the search index with the latest data. Wait for the indexing process to complete or manually trigger a re-indexing if needed.
Permissions and Security: Review the user permissions and security roles in your client development instance. Ensure that the users have the necessary access rights to view and search the cmdb_ci table. Check if there are any security constraints or ACLs (Access Control Lists) restricting the visibility of CIs in the search results.
Search Sources: Verify the search sources configuration in your client development instance. The search sources determine which tables and fields are included in the global search. Ensure that the cmdb_ci table is included as a search source and that the necessary fields for search are selected.
Instance-Specific Configuration: Consider any instance-specific configurations or customizations in your client development instance that may affect the visibility of CIs in the global search. Check for any custom business rules, client scripts, or UI policies that could impact the search behavior.

I will also recommended to compare the global search configuration and instance settings between your PDI and client dev instance to identify any discrepancies that may be causing the difference in behavior.

Mark as correct and helpful if it solved your query.

Regards,
Tushar

View solution in original post

Tushar · ‎07-13-2023

Hi Sai,

there could be a few possible reasons for this behavior:

Table Configuration: Check the table configuration of the cmdb_ci table in your client development instance. Ensure that the table is active and searchable. Verify that the necessary fields are present and configured correctly for search indexing.
Indexing Status: Confirm that the global search indexing is up to date in your client development instance. The search indexing process periodically runs in the background to update the search index with the latest data. Wait for the indexing process to complete or manually trigger a re-indexing if needed.
Permissions and Security: Review the user permissions and security roles in your client development instance. Ensure that the users have the necessary access rights to view and search the cmdb_ci table. Check if there are any security constraints or ACLs (Access Control Lists) restricting the visibility of CIs in the search results.
Search Sources: Verify the search sources configuration in your client development instance. The search sources determine which tables and fields are included in the global search. Ensure that the cmdb_ci table is included as a search source and that the necessary fields for search are selected.
Instance-Specific Configuration: Consider any instance-specific configurations or customizations in your client development instance that may affect the visibility of CIs in the global search. Check for any custom business rules, client scripts, or UI policies that could impact the search behavior.

I will also recommended to compare the global search configuration and instance settings between your PDI and client dev instance to identify any discrepancies that may be causing the difference in behavior.

Mark as correct and helpful if it solved your query.

Regards,
Tushar

SaiVasanth · ‎07-13-2023

@Tushar

I have tried with adding new custom table also it is working fine and showing results in global search. Only for this cmdb_ci I am not able to see.

Thanks & Regards,

Vasanth.