Using @DocChildren for response doc. autonumbering

I use @DocChildren in a column formula in a view where it evaluates the number of response documents perfectly. On a new response doc I would like to get the current number of current responses, but @Getdocfield does not produce the value of that specific column, while I can get the value of other columns’. I read somewhere that @DocChildren has a special output value. Any help is highly appreciated.

Elek

Subject: using @DocChildren for response doc. autonumbering

Hi Elek

I am not sure why you are using @getdocfield to access values from a view?!

@DocChildren is a formula in the view column and as such does not form part of the document data. It is merely used for display puposes.

What you can do is get the value of that column using @dblookup in your response doc using the Parent doc unid as the key. You would also need a view which is designed so that you can look up using the doc unids.

HTH

A

Subject: RE: using @DocChildren for response doc. autonumbering

Hi Arshad,

sorry, the info was not correct (getdocfield was a mistake). I used @dblookup and of course I have a view that contains the parent id in the first column (sorted). @Dblookup can return with all other column values from this view except the one where I have specified @DocChildren as a formula. However in the view I can see the correct number.

Subject: RE: using @DocChildren for response doc. autonumbering

@DocChildren returns special text which cannot be converted to a number and a good explanation as to why it is inaccessible from a view in this post:http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/a095a7eb1a941818852570f40064a853?OpenDocument

In which case I think you will have to resort to LotusScript to set the field on the response doc. Grab the parent doc and use the Responses property to get the number of existing responses.

A

Subject: RE: using @DocChildren for response doc. autonumbering

Indeed. The “Special Values” are calculated on the fly by the client, and are not stored in the view’s index. As DBLookup is reading the index, and not the open view you are seeing on the screen, you cannot get access their values that way. (Actually, I don 't think you can ever get their values.)