Hi everybody!I’ve got a problem with designing a reporting application. The thing is that I have some linked documents (I store the UniversalID in a field), bt they are not responses. If to display their interrelation I got used to form a page with response-like aligned links. But may be I can use a view for that purpose if I use a “hand-made” $Ref field? If anybody knows how to perform that trick I WILL be thankful for an advice.
PS or mailto:nectora@mail.ru
Subject: ??? emulating a response hierarchy
There is no way to do that in a view in the Notes client. You can group the docs together using categorization, but you’ll never get the indentation right. With a LOT of clever code, you can do it on the web. You MAY be able to do it in Notes 7 if you opt for a DB2 back-end (Query views aren’t available yet to test), but it isn’t going to happen in a satisfactory manner in ND6. If you need a response hierarchy, then you have to use a response hierarchy.
Subject: emulating a response hierarchy
Thank you, Stan,but I’ve successed doing what I wanted - with quite a few stupid code in LN6 :)_). By substitution of another RRL-field instead of $ref to the view - default $ref:=parentlink. The main trouble for me was creating such a field.
Subject: ??? emulating a response hierarchy
I think easiest wold be to set responses as REAL responses using LotusScript.
Depending on design and purpose of your applications you maybe do not need to resave documents to responses, but use a categorized view where you use parent’s unid as first column’s value.
Subject: RE: ??? emulating a response hierarchy
Quite pleased to get some help from a former compatriot 
) Thank you, Andrey, but if I could make it real responses there would be no problem and no question. I need to make a multi-level hierarchy from main documents. I know there is a solution, but I’ve lost its author - something like creating a fake $Ref (spec. type Response Reference List) and changing its value. By now I’ve tried my best with no result :(PS How is Sweden? Do you need more lotusmen from Russia there? )
Subject: Possible workaround
Hi Necto,
I don’t think this is what you are looking for, but my solution come using embedded views in form. You can use single category in the embedded view and set it to match the docID of the main documents.
That way, when you open the main document form, the embedded view contains the other documents linked to the parent.
Hope that helps,
Regards
Sergi M F
Subject: imPossible workaround
Thank you, Sergi,but the things oyu’re speaking about, are really no solution for me. With embedded view you’ve described you can get a one-level hierarchy, not multi-level.
PS Are you also a Russian?
Subject: RE: imPossible workaround
I saw this done once by a colleague but I tried it myself a week or two ago but couldn’t get it to work. but I know there is a solution that does work. i promise.
The solution is something like this. In your view SELECTion formula, put the following code on the before the “SELECT” statement:
DEFAULT $Ref := “MyField”
This makes the view behave as if the $Ref field exists on all documents and holds the value from the “MyField” field.
There’s another requirement I think - the docs either should, or should not, have a $Ref field on them. I can’t remember which it is (and this, I think, is where I came unstuck trying to do this myself last week).
I’ll mail the colleague who showed me it working and I’ll update this thread when I have the fine detail…
Subject: RE: imPossible workaround
Sorry, i think that should beDEFAULT $Ref := MyField;
(and not “MyField” in quotes)
Subject: Regards
Thank you, Phil!I guess I’ve got it. I’d be happy if I could help you somewhen - so feel free to mail me your questions mailto:nectora@mail.ru
With best regards,
Rost.
Subject: RE: Possible workaround
Albeit Nector’s solution is not provided by your advise, it does provide the solution to a future project I may have to work on. Would you kidnly post an example of how to implement an embedded view?
Warm Regards,
Francisco
Subject: Embedded view
What you need for using an embedded view:1) you define the class (form) for parent docs (your top-level, or main, docs)
you define the child class (as far as I see you need those docs not to be a real response, don’t you?)
there in the child docs form you define a field for linking a child to a parent - you may put there the parent’s UNID or any other unique identifier of the parent
you make up a view displaying ONLY CHILDREN, categorized by the first column, containing the values of your link field; you’d better make that column hidden
then you are to embed the view into your parent form (menu Create\Embedded Element\View…)
assign the Embedded View “Show single category” property (Designer pane) to your key field name (without quotes - Keyfield not “Keyfield”)
enjoy. You may search in Designer’s Help for “Embedded view”
Good luck!