OData Table refresh
Peter_Miklian
Customer Advanced IT Monkey ✭✭✭
Hi,
we want our Service Desk (SD) to oversee Resolved IR and close them only if their Resolution Description has desired quality. They use the Primary Owner field to distribute tickets to specific analyst (as the Assigned To field is filled with the analyst who resolved the IR).
@Gabriel_Lences built dashboard to show these (and other relevant) attributes using OData Table Widget.
When SD analysts updat any IR and saved, it take like 8 minutes to show the change in the Primary Owner field on the dashboard. Could you advise how to speed this up or where could be the issue if the dashboard should reflect changes immediately? Thanks.
Best Answer
-
Simon_Zeinhofer
Customer Ninja IT Monkey ✭✭✭✭
@Peter_Miklian The oData widgets take their data from the platform and therefor the cachert.csnCached.... tables from the Servicemanagement Database.
The data from the productive DB gets synced into these cached tables every few minutes, afaik it is 10 minutes out of the box. You can change the sync time under
Admin Settings - Dynamic Data Settings
We have it set to every 3 minutes now, but since 11.8.4 sometimes the performance seems to be impacted by the dynamic data sync. But to your question I guess it is neither possible, nor wanted, that the data in the cached tables reflect changes immediately.
2
Answers
@Peter_Miklian The oData widgets take their data from the platform and therefor the cachert.csnCached.... tables from the Servicemanagement Database.
The data from the productive DB gets synced into these cached tables every few minutes, afaik it is 10 minutes out of the box. You can change the sync time under
Admin Settings - Dynamic Data Settings
We have it set to every 3 minutes now, but since 11.8.4 sometimes the performance seems to be impacted by the dynamic data sync. But to your question I guess it is neither possible, nor wanted, that the data in the cached tables reflect changes immediately.
@Simon_Zeinhofer thank you for explanation. As you say, we won't change default settings because of performance impact risk. We will amend our process instead ;)