- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-07-2024 11:19 PM
Hello all, can you please help me to understand why the typeahead search is not working in service portal of higher instance as it is working in development instance with all same configurations, Any suggestion is appreciated. Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2024 01:31 AM
Sure, there could be several reasons why the typeahead search is not working in the service portal of a higher instance. Here are some possible causes and solutions: 1. **Different Data**: The higher instance may not have the same data as the development instance. Make sure the data is consistent across instances. 2. **Configuration Differences**: Even though you mentioned that all configurations are the same, it's worth double-checking. There might be some overlooked differences in the configurations of the two instances. 3. **ACLs**: Access Control Lists (ACLs) might be preventing the typeahead search from working in the higher instance. Check the ACLs to ensure they are not blocking the search. 4. **Browser Cache**: Sometimes, the browser cache can cause issues. Try clearing the cache and see if the problem persists. 5. **Scripting Errors**: There might be some scripting errors causing the issue. Check the browser console for any errors. 6. **Service Portal Widgets**: The issue might be with the Service Portal widgets. Check the widget configurations and scripts. 7. **Instance Synchronization**: If the higher instance is not synchronized with the development instance, it might cause issues. Make sure both instances are synchronized. 8. **Typeahead API**: There might be an issue with the Typeahead API. Check the API for any issues. 9. **ServiceNow Updates**: If the higher instance has been updated recently, it might have affected the typeahead search. Check the ServiceNow updates. 10. **User Permissions**: The user might not have the necessary permissions to use the typeahead search in the higher instance. Check the user permissions. Remember, it's always a good idea to reach out to ServiceNow support for assistance if you're unable to resolve the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-08-2024 01:31 AM
Sure, there could be several reasons why the typeahead search is not working in the service portal of a higher instance. Here are some possible causes and solutions: 1. **Different Data**: The higher instance may not have the same data as the development instance. Make sure the data is consistent across instances. 2. **Configuration Differences**: Even though you mentioned that all configurations are the same, it's worth double-checking. There might be some overlooked differences in the configurations of the two instances. 3. **ACLs**: Access Control Lists (ACLs) might be preventing the typeahead search from working in the higher instance. Check the ACLs to ensure they are not blocking the search. 4. **Browser Cache**: Sometimes, the browser cache can cause issues. Try clearing the cache and see if the problem persists. 5. **Scripting Errors**: There might be some scripting errors causing the issue. Check the browser console for any errors. 6. **Service Portal Widgets**: The issue might be with the Service Portal widgets. Check the widget configurations and scripts. 7. **Instance Synchronization**: If the higher instance is not synchronized with the development instance, it might cause issues. Make sure both instances are synchronized. 8. **Typeahead API**: There might be an issue with the Typeahead API. Check the API for any issues. 9. **ServiceNow Updates**: If the higher instance has been updated recently, it might have affected the typeahead search. Check the ServiceNow updates. 10. **User Permissions**: The user might not have the necessary permissions to use the typeahead search in the higher instance. Check the user permissions. Remember, it's always a good idea to reach out to ServiceNow support for assistance if you're unable to resolve the issue.