View selection..this should be easy

I am using @Picklist to return a set of docs. The view I used during testing used all docs using Select @All.

I now have the basics down and it works, so I need to refine it. I want to limit the docs returned to only those created with a specific form. So I try the simple search function and it generates the following: SELECT ((Form = “NewAddress”) | (Form = “NA”)). I don’t see anything wrong with this, but it does not work. I know the docs I am looking for use this form because one of the columns displays the form used, and it is correct. Well it’s been quite awhile since I did any developing, and I vaguely remember this type of problem so I decide to try and skin this cat another way.

I try Select @IsResponseDoc as the forms create response documents. No luck.

In both cases I get no documents.

Any thoughts?

TIA

Joe

Subject: View selection…this should be easy

Oh, you are GETTING documents alright – you just can’t see them because you have “Show response documents in a hierarchy” selected on the “i” tab of the view properties dialog. When that is selected, response documents can only be displayed as responses to their parents, and since you aren’t selecting the parents into the view you can’t see the responses either. Deselect that property and all will be well.

Subject: RE: View selection…this should be easy

Thanks Stan, that did indeed resolve the issue I posted. But it caused another issue, now the picklist isn’t going to work because the docs arent under their parent docs in the view.

Back to the drawing board.

Thanks a ton though, I appreciate it.

Subject: RE: View selection…this should be easy

You haven’t really fully explained your requirement.

If you want to have the response documents to a single parent display grouped together, you could always categorize the view by some key value that the response documents have in common.

If nothing else, you could categorize by the value @Text($Ref), which while not pretty, does group them together. This is probably best used in conjunction with the categoryname argument of @picklist, which lets you limit display to a single category.

If the responses have no key value in common, you could arrange for this with an agent that updates them with some copied value from the parent.