This post got me wondering if there was a bug, so I tried some experiments with it. The last post is correct, that the mondrian cache is flushed with the following line of code, which is what the "Flush OLAP Cache" button does: mondrian.rolap.CachePool.instance().flush(); However, JPivot keeps its own (smaller) session based cache, so logging out after flushing the cache is necessary to clear your session if you have already loaded a particular analysis view in the current http session. And, as alluded to in another post, if aggregate tables are used, they might hide changes to base data. For example, I changed sales_fact_1997 in foodmart by multiplying unit_sales by 2, then I flushed the cache and logged out, but did not see the changes until I went back and disabled aggregate tables (and then flushing the cache and logging out again). If you are using aggregate tables, the proper thing to do would be to rebuild or update those when the underlying data has been updated. HTH, Sam