We have several SPOFU views in a rather large database that is replicated out to several hundred users.
The users have been given the ability to “create private views/folders” in the database ACL.
I believe this was done to allow for automated private view removal if there is a change in the design of the “parent” view from which that view inherited its design (did that just make sense?).
In any case, this has led to the creation of literally thousands of private views in the server-based replica of the database.
These can be seen by reviewing the log document for that database.
Is there any way to allow users to create these private views, but NOT replicate them back up to the server?
We were looking for some sort of selective replication setting, but that doesn’t seem to offer the ability to distinguish this sort of thing.
With the ACL checkbox turned on, the SPOFU views are on the server, which allows them to be manipulated by someone with full access rights. Without the checkbox turned on, the SPOFU views are on the user’s desktop only, which means they don’t take up room on your server, but you can’t touch them without writing code to execute on the desktop.
You don’t lose programmatic access to the views, you just lose server-side access (scheduled agents, run-on-server agents, web agents, that sort of thing). Code running in the client can still access the views.
This is code that I’ve inherited, and I noticed it wasn’t working as expected after modifying the database ACL.
I’ll have to hit the drawing board when I next get a chance to review it, and see if I can’t revise it to work properly without the ACL setting enabled.