Error with embedded view with single category selection

HCL Domino Domino Forum
1

I found this strange behaviour of embedded view.

In a form we put a view with a “show single category” selection (on a selection_code_field)

selection_code_field

…>MAIN TITLE

…>FIRST LEVEL TITLE

…>SECOND LEVEL TITLE

…>etc.

When I open the form the first time I got an expanded view as normally.

In the embedded-view we have a button with this code :

@Command([RefreshFrame]);

@PostedCommand([NavigatePrevMain]);

@PostedCommand([ViewCollapse]);

@PostedCommand([ViewExpand])

which normally (from R6.0 till now) collapsed the view on the first level:

  • Main title

…+ first level title (1)

…+ first level title (2)

…+ etc.

Now I got a collapsed view with the first line blank or showing the selection code field:

  • selection_code_field

…+ main title

while selection_code_field should be always hidden.

Users (fortunately not so many in 8.0.2) are burning my phone…

IBM could you help us?

2

Subject: This works for me

@Command([RefreshFrame]);@PostedCommand([ViewCollapseAll]);

@PostedCommand([ViewExpand]);

@PostedCommand([ViewRefreshFields]);

3

Subject: Yes, but this is not the point.

Hi Torben.Thanx for your code.

Actually the problem seems to be with the instruction:

@PostedCommand([NavigatePrevMain]);

In 8.0.2 Notes understands we mean the real MAIN category in the original view, that’s to say the “selection_code_field”, while in previous releases the MAIN category was the one showed in embedded view.

However I got your suggestion and with this code:

@Command([RefreshFrame]);

@PostedCommand([ViewCollapseAll]);

@PostedCommand([ViewExpand]);

@PostedCommand([ViewRefreshFields]);

@PostedCommand([NavigatePrevMain]);<-- you got the (?hidden?) selection_code_field

@PostedCommand ([NavigateNext]);<-- you got the intended main category

@PostedCommand([ViewCollapse]);

@PostedCommand([ViewExpand])

this way I got only a blank row (sometime the selection code…) at the top

I will insert two actions one pre and another post= 8.0.2.

Can we hope to have this bug fixed in next release?

Many thanx again.

Marco