Refresh Rates in Embedded Reports

Usually in work centers’ overviews, you find embedded reports. Once adjusted to your needs, they can help an end user in performing his daily task. Nevertheless, they do have an impact on how fast the overview is being loaded. To mitigate this impact, it is possible to define a Refresh Rate for each report.

Now, I got a very good question – and finally got it: “What is the difference between refresh rate <1 hour> or <1 hour tolerant>?”

So, here’s the answer: In general, the refresh rate defines how long a report result is being retrieved from cache to speed-up this view. Once the defined refresh rate is passed (e.g. longer than one hour), it retrieves the data from the database, not the cache, and stores them in the cache again for the next hour.

But – what should happen in case there is an empty report result?

• The first option (“1 hour”) tries to recall data from the database each time the overview is being displayed, as long as no valid result has been stored (e.g. a sales order volume list for the past month).
• The second option (“1 hour tolerant”) accepts an empty result – and will not try to redetermine data before an hour has passed (e.g. for a daily sales order list – perhaps won’t show any result when you start your work at 8 am).