I know that the documentation says “You should not use @UserName in a public view, doing so will produce unpredictable results.” - the unpredistable results being the server doesn’t always show just one users’ documents - and the results seems to vary based on server load. The trick here is that this problem is not always immediately obvious.
However, if I create a single category embedded view in a page and specify @UserName for the single category value, it appears to work, but I am not sure if this is the same concept, and may also lead to “unpredictable results” - or if this is a safe way to go…???
The use of single category embeded view will work fine as long as you need to show Documents of user A to A alone and documents of user B to B alone. This will not work if there a user C who needs to see documents of both A and B.You can use “Private on first Use” views.
When creating the view you can specify the view type as Private on first Use" and you can use @username in the view/column formulas.
This way a new privaye view will be created for every user who opens the view. This will aviod the “unpredictable results”. Morover if the database is a bulky one and if there are lots of users then this may not be a very effecient way.