Are you connecting Xtraction to Service Now directly via the ODBC driver?
If so, here are a couple of options that may help:
- Turn on the Aggregate Web Service plugin, which can improve the ODBC driver speed when aggregating data
- Add the glide.cache.size.syscache_tabledescriptor property to the Service Now instance. Customers that have given this property a value of 5000 have observed a significant performance increase in Xtraction performance and iSQL queries to their Service Now instance. You should consult with your Service Now partner/vendor before implementing this property to be fully aware of how it will affect the instance.
Thanks but after activating Aggregate Web Service in ServiceNow, Group Component in Xtraction is not working
You have to make sure, you have an access to ServiceNow Mid-server
Thanks pbalamut , Can you pls. elaborate what you mean by access to ServiceNow Mid-Server?
Does it mean that the Xtraction acct being used to connect to ServiceNow via ODBC should have access to Mid Server?
All of the customers that I've helped set up Xtraction reporting against ServiceNow have used our solution of syncing the ServiceNow data to a local copy and reporting off of that. Since it syncs every 5 minutes, that is usually an acceptable refresh time (the data does not get too stale). That would not be acceptable for phone data; but should not be an issue with service management data.
If you are pointing Xtraction directly at the ServiceNow ODBC connection, I would expect to see less than stellar response times for dashboards due to the delay of the Internet travel and SN's server response times.
If you are still encountering problems, I would suggest opening a support ticket. While you are at it, I would suggest attaching the log file to the ticket or putting Xtraction in debug mode and attaching a screenshot of the error that appears when using the Group Component.