Link to home
Start Free TrialLog in
Avatar of yukinko
yukinko

asked on

Notes/Domino : Can change view SELECT condition by settings in another DB?

I have a view in DB A. Then I have some settings in DB2. I'd like to change the view SELECT condition in DB A by DB2 settings. Is it possible? If not, how to generally solve this case?
Avatar of Sjef Bosman
Sjef Bosman
Flag of France image

View conditions (the SELECT?) should not be changed. If you really have to, you can change the SELECT programmatically indeed. If you have a database with many documents, it'll take quite some time to update the view.

General solution: keep the view simple, and use FTSearch if you need more detals.

Can you describe your situation? Why do you want to modify the view's SELECT?

PS it is not possible to do queries based on data from 2 different databases in Notes. The only way is to put everything in one database...
Avatar of yukinko
yukinko

ASKER

I have a view which have a very simple SELECT string. The view lists business approvers in a company.
However this time I have to modify this DB. There is a requirement which can change the approvers by settings in another DB. The settings are  business titles, departments, tentative approvers, etc. I mean the approvers are changed by the settings.
The company has huge employees and there are many business titles, departments, tentative approvers. The SELECT/query will be very complex. Of course I don't think this settings are frequently changed.

So I think the best solution is to change SELECT when the settings are changed. The reason why I'd like to use the option is I need to list them as WEB UI for end-user. If I can use the view as data source, I think it is easy to use XPages view control. However if I use FTSearch option, it is not easy to prepare the WEB UI.

Please advise me.
I'm guessing here, so please don't shoot me...

Approvers and other groups of people in a Domino environment are usually put in the Domino Directory (names.nsf) in a Group document. In that way, these groups can get their own entry in the Access Control List (ACL) of the database, if needed with a role like Approver or so, or to give them other privileges.

The usual approach when you have information in one database that you need in some other database is to make a scheduled agent in one of the databases to copy information over. You can copy the info to documents (new or updated) or you can modify the ACL directly.

If someone becomes an Approver, shouldn't his/her name be in some Approvers field in a document? So that you can create a categorized view with Approvers in the first column?

PS Forget SQL and relational databases... ;-)
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.