Is there a way for user to see all the documents in a database (on a view) even if that user is not on the reader or author field? Thank
Subject: Author and reader fields
There is no good or direct way to do that. You could have an agent running under different permissions periodically run a report summarizing the data into a document which more users could see, but that’s not something I’d want to try without a gun to my head.
Subject: Author and reader fields
as far as I see, there isn’t a way to do this.
Subject: RE: Author and reader fields
Like I said, no good way to do it. So, then, why do you want to? What objective are you trying to achive?
Subject: RE: Author and reader fields
This is what I can do, I can create responses to my main documents. My responses will contain the information I want from the main documents. This responses will not have author or reader fields. Thn I will display it on a view.
That is a very good way to do it.
However, I am trying to avoid doing it. Before I do this, I would like to know if I can use my main documents that contains “'reader” and “author” fields. And every single use will see the documents on another view that I will create.
Subject: RE: Author and reader fields
The more usual technique is to put all the public information in the main documents and put the protected information in responses with readername fields. That tends to be less work. But your way is possible, and if you’ve already got the bulk of your application written it may be the best way to go.
Other ways that people try to do this – with hide-whens, etc., are not secure.
Subject: RE: Author and reader fields
Hi Danny,
I’m not quite clear about what you want. Are you saying that because users cannot see the original main document, they can’t see your responses? If so, create a view with the property ‘Show response documents in a hierarchy’ unchecked and then all the responses will show in there regardless of whether users can see the main document.
hth
Tony
Subject: RE: Author and reader fields
Sorry, but you should had read my first post. My main documents have reader and author fields. Therefore; not everybody will see all the documents unless you are in these 2 fields.
So, I will create a view to show only information from these documents to everybody. But my view have to be able to sort. Is there a way for me to show the information to everybody even if they are not on the reader or author fields?
I was thinking to create some responses documents without the reader and author fields. Then collect the information from the main documents and display it on a view for everybody.
Before I do what I want to do, I want to know if there is a way for me to use the main document and avoid creating responses.
Wow, I just wrote the whole post again.
Subject: RE: Author and reader fields
The short answer is No. You can not do it. You will need to generate separate documents with the publicly viewable information. Whether you make them children, parents, or siblings is up to you. In my experience it’s simpler when the public information is the parent and the private is the response, but it works either way.
The long answer is what Andre already said: the only thing you can do is create categorized views that shows a sorted hierarchy of data. This feature (it used to be widely considered a bug!) is ugly, but it does expose data from readername protected docs to all users at the view level. You can show one field per line, indenting each line, then going back to the left margin for the next doc, etc., etc. This will be re-sortable, but it will almost certainly not look like anything that you would want. Or you can combine multiple fields per category entry and display just one line per document, but you’ll have to take control of the fonts and spacing to make it look good, and you’ll have no re-sorting capability. Overall, this is not a good solution. I doubt you will be happy with it.
Subject: RE: Author and reader fields
At view level, how I can do that? I I did not see any document after I set the columns to be categorized. Unless I am on the reader fieldThank
Subject: RE: Author and reader fields
You don’t actually see the documents. You just see the categories even though they appear to be empty. (I.e., no docs after you click the twisties.) That used to be the default behavior. Don’t recall if it still is the default, or if you need to turn on a setting somewhere to make it happen. As I said, most of us considered this behavior to be a bug since back in release 3.0.
Subject: RE: Author and reader fields
No; it’s only possible for them to see the category headings that contain those documents (and then only if the view design allows that).
Of course, as the developer you could circumvent that by providing them a text report of the documents, if you chose.
Subject: RE: Author and reader fields
How do you do that? Can it report be refreshed? Can this report alow me to sort?Thank
Subject: RE: Author and reader fields
You create an agent that runs on the server, either on a schedule or on demand from users via NotesAgent.RunOnServer method. The agent creates a document, adds a Body rich text field to it, and uses the methods of NotesRichTextItem to write the report into the Body field. It then either mails the document to users as a memo, or stores it into the database where users can find it.
Subject: Author and reader fields
Yes there is, but it can’t be just “any” user. It has to be someone who is listed in the server document as a “Full Access Administrator”. Then the user just fires up the Domino Admin client, connects to the server where the database lives, goes to the Administration menu, selects Full Access Administration, and then opens the regular client and opens the database. Voila! All the documents are visible. Full access stays active until you either turn it off or you shut down the Admin client. (Note: I’ve had inconsistent luck with turning on Full Access privileges while the Notes client or Desginer are already running, so I recommend shutting everything down except the Admin client before turning it on.)
In earlier releases you could open the database on “Local” and get the same effect – but security is always enforced in local replicas in current releases, so now we have the reverse of what we used to. I.e., if the database isn’t on a server, you’re out of luck.