We have an application that uses Private on First use Views to show a user’s calendar entries in a case docketing application. The user can easily see just their information and weed out everything else, and then with Federation can overlay this information onto their personal calendar to get an overview of all they’ve got going on.
It’s really pretty slick… if it was reliable. The private views combined with calendar overlay is something I’ve been wanting a long time. It seems that these private views lose information, or just don’t update. You kill it on the backend and let them rebuild it, and it’s fine for a couple of days.
Is there a correctable reason we’re experiencing this? Are POFU views just that buggy?
It appears from looking in previous version forums, Private on First use views has been an ongoing, unreliable design element.
If it’s so bad, why is it still an option? Do folks just not care about reliable data? Why not take it out so one doesn’t waste hours of time trying to get something to work that has no hope of succeeding?
Subject: Heh, want some real fun with stuff not working as advertised? Turn on “Optimize Document Table Map” in your DB properties and watch your views get FAST… and flakey.
It’d be great if the Designer Help said “Note: this feature may cause your view indexes to be flat-out wrong.”
Subject: how we deal with ‘private on first use views’
Hi,this doesn’t directly answer your questions, but I just thought I’d mention that we recently wrote a short article on how we deal with ‘Private on First Use Views.’ It contains some code that might come in handy: