CODEWITHSUNDEEP
xpages
Maryam
Maryam

Reputation: 71

Xpages, Inherited documents in view panel by using @Unique

I have two forms project(Document) and comment(Response to Response) I want to create a view that displays all comments of selected Project

Any help would be appreciated.

Upvotes: 1

Views: 671

Answers (2)

Bill F
Bill F

Reputation: 2087

I moved away from using Parent and response documents in Notes years ago because they were just too much trouble. I also moved away fro using the UNID as the 'link' for several reasons. The first is that the UNID can change (resolve a save/rep conflict) Second archiving is all but impossible because again the UNID changes when the document is copied to another DB. So when I create a 'parent' document I store @Unique into a field I call LinkKey, and store that value in all 'response' documents. When I create the response then I store a new @Unique into a field rLinkKey. This way a response to a response knows it's originator (LinkKey) and it's direct parent (rLinKey). Now you can extend this any number of levels deep fairly easily. This worked OK in native Notes with some kludge, but now in XPages with repeat controls the real power comes from nested Repeat Control. Something I have always wanted to do in Notes but was never able to is now a piece of cake. The down side is that getDocumentByUNID() is going to be faster that getDocumentByKey(LinkKey, true) but the other advantages far out weigh the unnoticeable time difference (IMHO)

Upvotes: 1

Patrick Sawyer
Patrick Sawyer

Reputation: 1382

I love doing this type of stuff in xPages.

For a moment, don't think about project and response. Think uniqueID. In order to make the project document reference the comment you add a unique ID to each of them that will reference each other. Don't use response docs in xPages, there is no need I see. When you save the comment, save the unique ID of the parent document to a field on the comment document by referencing this value where document1 is the datasource of the parent and document3 is the document of the child.

   <xp:modifyField name="uid"
        value="#{javascript:document1.getDocument().getUniversalID()}" 
        var="document3">
    </xp:modifyField>

Now that you have a bunch of parent and children docs, you create a categorized view where you are only capturing the comments. Use a view selection formula to exclude the parent form. Make the first column the uniqueID that you previously captured. You now have a view that will keep all the comments categorized by the unique id of the parent.

View Categorized by UID

Now in the xpage you now need to filter on the key value. You filter by computing the keys to the value of the parent document. Here document1 is the parent.

 <xp:dominoView var="view2" viewName="rejections"
        keys="#{javascript:document1.getDocument().getUniversalID()}">
    </xp:dominoView>

The great thing about doing this is it will work in a viewPanel, dataView, or a repeat control since you are referencing the data not the UI.

If you wanted to do comments of comments there are a couple of approaches but I think they would all have the same structure. If you made it this far start looking at repeat controls they will let you break free of the normal notes views.

Upvotes: 2

Related Questions