Tiles and cache

Szymon Zaleski

Couple weeks ago I needed to collect Blackbaud nameid from our database users, so instead of creating a new tile just for that, I added some code to the existing tile on Constituent tile dashboard, that would log whenever NXT user opened a constituent record. Two weeks later I only had about a half of the names and it was a bit terrifying to realize that people who should be using NXT and accessing constituent records are not using it as much as they should. However, at some point I asked one of the people to open a record, watched them do it, and there was no trace of it in the logs. Only after I asked them specifically to reload the frame, the logs started showing up. Which means, for two weeks, NXT was loading the old, pre-logged, version of the tile.

I turned off caching in IIS where the tiles are located - it didn't do the trick. I actually added meta no-cache to the tile's index.html and it didn't help either. The tile must have been already cached and even the change to the html did not make a difference.

What needs to be done to assure that every time we update the tile, the NXT will display the new version?