Display in View only by username

HCL Domino Domino Forum
1

Hi

I am trying to create a view, which only displays the documents based on the persons username.

This is for a change request database, and I want the developer to only see work that is assigned to him.

In the Assigned to column, I have the following, but it does not seem to work

@Name([CN];@Username)=change_request_developer

Any ideas;

Thanks

sCott

2

Subject: Display in View only by username

Look at including Readers and Authors fields. That way, only the people listed in these field can read and/or modify the document. And it doesn’t show up in the view if the person isn’t in the Readers field.

Remember to include a developers group or role in the Readers and Authors fields or you won’t be able to see the documents either.

3

Subject: Display in View only by username

If the developers are using notes clients (seems like they would) create a shared > private first use view - with the selection formula @username = change_request_developer

4

Subject: Display in View only by username

Well, as if there were not enough answers yet …

… but since the suggestions are so different, I’d like to line them up one by one.

Readers fields

If one developer must not be able to see another one’s CRs, you HAVE to use readers fields. No need for any other action, documents, a developer is not allowed to see will just be invisible. If displaying a personalized list is just a convenience feature, do NOT use readers fields, as they will drag performance unnecessarily, then.

Shared, private on first use views

They will do what you need (if security is not a concern), since you can personalize them using @UserName. But from a maintenance point of view they are pretty much a nightmare. E.g. refreshing those private views after making a design change to the original view requires quite a bit of additional work.

Single category embedded view

My personal favorite (again, if security is not a concern), I have to admit. You would categorize the view by a field containing the developers name and provide @UserName (or a converted form like @Name([CN];@Username), whatever is in the field) as the single category selector. Very easy and slick. In really big views, performance will be somewhat degraded compared to the private view.

For a non-embedded view, you can have the same sort of functionality using @SetViewInfo.

5

Subject: Display in View only by username

@Username should not be used in a public view as it produces unpredictable results.

You need to use a single category embedded view. The notes help for @username provides a link with instructions.