Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 287
  • Last Modified:

View containing fields from different forms (cross-tab) possible?

Hi Experts,
I am currently working on a redesign of a LN database and stuck with one issue, hope you can help me:

I have 3 forms each linked with the others via a keyfield.

Form A:
some fields like Letternumber, date, etc... and
embedded view showing all related forms B (via field Parent ID = @DocumentUniqueID of Form A)

Form B:
again some fields eg start date, end date and
embedded view showing all related forms C (via field ComponentID =@DocumentUniqueID of Form B)

Form C:
basically 2 fields: Component Name and Component Qty

Now I am trying to create a view provided me with an overview of fields cross the forms:

Header: Letter number | Date | StartDate | EndDate | "CompName - FormC" | "CompName1"
Values:  FormA -Letter | FormADate | FormBstart | FormBEnd | FormCcompqty | FormC1compqty
              FormA -Letter | FormADate | FormB1start | FormB1End | FormCcompqty | FormC1compqty

I was thinking about computed cloumns to create this view however I am not sure if this is the right approach, please help.
0
Wasp790218
Asked:
Wasp790218
  • 2
1 Solution
 
Sjef BosmanGroupware ConsultantCommented:
You can have a view with multiple different forms. I assume from your description that you didn't use the Notes built-in document-response relationship, but instead you created your own. Even then it should be possible, but ONLY if all documents contain the same sortable fields, so you can categorize the documents based on form as well as some fields. If ALL you have is ParentID and ComponentID, and form C does NOT contain the ParentID, you can't make this work. And even then the view won't please you, because you need names and not IDs in the view to make it really usable. Categorizing on some document-ID is technically enough but sucks in a view.

IMHO this looks like the classical mistake made by an SQL-expert who constructed a 3rd normal form database in Notes. Won't work in Notes, ever. Notes needs redundant data.

A two-stage suggestion:
- create an agent that applies the document-response relation in the database, the real thing
- create a hierarchical view that uses this relationship

It will create only one additional field in all response documents, created by forms B and C (the field $Ref).

There's one snag: in order to continue to use the hierarchical view, you have to update all places where response documents are saved (forms B and C). Properly maintaining the relationship is vital. Also, if you delete a formB document without deleting all its sub-documents will create orphan documents. By the way, that would happen in the original setup as well, so that shouldn't be a big surprise.
0
 
Wasp790218Author Commented:
Have not rated as A as it did not solve my issue put pointed me to the correct solution as LN has a reduntant data model which i did not consider in my approach initially.
0
 
Sjef BosmanGroupware ConsultantCommented:
Sheesh, you run a tight show... :-P

What does it take to get an "A" ?? For all I know, the answer was correct (it cannot be done), I told you why, and I told you how a solution could be achieved. What else could I have done??
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now