• NamePicker does not work on a 'XPage associated with the document's form'

    By Cameron Gregor 1 decade ago

    If I put a name picker on an xpage that was navigated to from a view control using the open with 'XPage associated with the documents form' I get an error

    and server Console shows error:

    HTTP JVM: com.ibm.xsp.webapp.FacesServlet$ExtendedServletException: com.ibm.xsp.FacesExceptionEx: Unable to get document page name for null

    However if I change the navigation of the view control to explicitly set the XPage to load, the picker works as expected, I am assuming that there is a 'pagename' type variable somewhere that is not set when using the auto-choose-xpage option.

    The namepicker source is as follows

     

    <xe:namePicker id="namePicker500" for="djextNameTextBox500">

<xe:this.dataProvider>

<xe:dominoNABNamePicker people="true" groups="false" nameList="people">

</xe:dominoNABNamePicker>

</xe:this.dataProvider>

</xe:namePicker>

<xe:djextNameTextBox id="djextNameTextBox500" multipleSeparator="," multipleTrim="true">

</xe:djextNameTextBox>

     

    • I've not been able to reproduced this,could you attach a sample?

      By Paul Hannan 1 decade ago

    • I have the same problem

      By Steve Cochrane 1 decade ago

      Thanks!

         Once I changed the view controls to open the specific XPage, the namepickers worked fine!  Very strange.

      Paul,

         To test, create a simple XPage with a namepicker to an inputtext control.  Create an XPage with a view control, and set it to "Open page associated with form".  A new document will work fine, but if it's been saved, and in edit mode, you'll get the same error message as above.

      Steve in NYC

      • Same Problem

        By Alex James Woodall 1 decade ago

        I'm having the same problem:

         

        <xp:inputText id="AddRecipientNamePickerField">

</xp:inputText>

<xe:namePicker id="AddRecipientNamePicker"

for="AddRecipientNamePickerField" dialogTitle="Add a Recipient">

<xe:this.dataProvider>

<xe:dominoNABNamePicker addressBookDb="names.nsf"

groups="false">

</xe:dominoNABNamePicker>

</xe:this.dataProvider>

</xe:namePicker>

        Works fine via

        ER.xsp?documentId=68701E22E99A616480257B2F00349160

        but not via

        $$OpenDominoDocument.xsp?documentId=68701E22E99A616480257B2F00349160

        And in the log.nsf I get

        15/03/2013 11:37:03   HTTP JVM: com.ibm.xsp.webapp.FacesServlet$ExtendedServletException: com.ibm.xsp.FacesExceptionEx: Unable to get document page name for null

        Has anyone found a fix for this? Passing the "xpage to open" from the view isn't ideal as I'm using the Dynamic View control inside my own control that's inherited from my standard base design into multiple applications that have different xpage names etc.

    • Similar problem with name picker

      By Doug Phillips 1 decade ago

      I am having a similar issue.  This is admittedly my first attempt at xpages, and thus the extensions.   I do not get any errors in log.nsf. I like the others have to be creating a new document for the name picker to work at all. Then i see just the local address book.  Attached is the error i see when using the notes client. From the browser I see no errors,  but get no picker.

      <td>Category Nametd>

      <td>

      <xp:inputText id="inputText1" style="width:200px"

      value="#{document1.CategoryName}">

      xp:inputText>

      td>

      tr>

      <tr>

      <td>Category Valuestd>

      <td>

       

      　

      <xp:inputText id="inputText2" value="#{document1.CategoryValues}">xp:inputText>

      <xe:namePicker id="namePicker2" for="inputText2">

      <xe:this.dataProvider>

      <xe:dominoNABNamePicker

      addressBookSel="all">

      xe:dominoNABNamePicker>

      xe:this.dataProvider>

      xe:namePicker>

      td>

       

       

       

       

      • Same issue here - possible cause

        By Steve Smillie 1 decade ago

        I have this same issue.
        I think this is because the field on underlying form is of Type "Names" instead of "Text".

        If I create new documents, no problem. 

        • My XPages isn't making that field a Names field.
        • On an existing document, where the data is in a Names field (document created in Notes), I get this issue.

        Can someone verify my cuase?
        Any solutions?

        My environment is still 8.5.3 with  Ext Lib 8.5.3.20121217-1354
        Perhaps fixed in Domino 9.0 or the Ext Lib for 9.0?

        • By Edward Xuereb 1 decade ago

          Hi

          I have fixed this issue by changing the url in the beforeRenderResponse stage, and redirecting to the new url. This is not ideal because it is creating two requests, but it's the only solution that I found so far.

          Old URL:

          http://[db_url]/%24%24OpenDominoDocument.xsp?documentId=[unid]&action=editDocument
          New URL:
          http://[db_url]/[xpage_url]?documentId=[unid]&action=editDocument