Sub view possible?

HCL Domino Domino Forum
1

Dear all,

i need to create a new view in a self-designed Lotus Notes database.

Alright, what’s the problem?

The view that should be created is nearly the same as an already existing view.

So my question is:

Is it possible to create a view out of a view (= subview) and filter some additional data?

For example having a view B, that displays all entries from view A and filters some more entries.

I would like to have a “master view” and then use this view in many other views, which only need some little more filtering. → inheritance

Many thanks!

2

Subject: Not directly.

But you could create the master view first, with all/most columns being “shared columns”. You then copy this view, rename it and change the selection criteria and any columns you need to change.

If you want/need to change a specific column everywhere, you just edit the shared column and all views will be updated.

3

Subject: Thanks, but…

Thanks for your reply!

Shared columns are nice, but in my case, the columns don’t change in the different views, only the selection criteria is changing.

An example:

We have a Notes database which contains all our managed servers.

I have a view A, which shows only our SQL servers (where field x is set to “SQL”).

I want to create a view B, which shows only our virtual SQL servers (where field x is set to “SQL” and field y is set to “virtual”).

I would like to use view A and only add one more selection criterion (where field y is set to “virtual”).

It would help preventing tipping errors and much faster updating, when views must be changed. (only update the master view).

In SQL i can create a new view and then make a new SQL select statement which uses the view plus i can add some more filter criterias.

→ I am missing a feature like this.

4

Subject: Search?

Build canned, shared searches; you can have one view with all of the data, then just invoke a canned/saved/shared search. Build as many as you like.

If you actually need no kidding live views all the time, then you have to build one view per selection statement.

Notes <> SQL, Notes= NoSQL. Different beasts.

5

Subject: Another option…

Is build the master viewThen have an agent that requests the new selection formula - maybe by using a checkbox - and builds a new temporary view by copying the master, giving it a new (easy-to-identify-programmatically) name and edits the selection formula

Then have a scheduled agent that runs, say, nightly to purge all of the temporary views

If you need these long term, then change all that slightly, have an agent that runs when needed to purge the existing non-master views and recreate them from the (presumably edited) master, only with their own selection criteria