xpages

I needs some tips on this one, since I couldn't find anything on this, though it's probably pretty simple to do, but I can't think of a way. Ok, so I need a hidden field which will automatically compute so called id numbers for every document, the numbers must start from 00001 and forward and must never ever repeat. For instance i create a document with numberId = 00001 and another document which creates numberId = 00002, if I ever delete the first or second document, the third created document should have numberId = 00003. No matter how many documents get deleted, the next document created

I have an EditBox control in a repeat control. Its iteration formula is: return 5; It is successfully displaying 4 edit boxes (the starting index is set to 1). In SSJS, how can I get the value of the nth Edit Box? You could set a sessionScope variable (or any scope variable) on the onchange event of the edit box and then in your SSJS reference the sessionScope variable. Here is some sample code, the bottom bit just shows your sessionScope variables on the page. <?xml version="1.0" encoding="UTF-8"?> <xp:repeat id="repeat1" rows="30" value="#{javascript:5}" indexVar="rptIndex"> <xp:inputText id

In my XPages application, I want to debug a problem related to javax.net . Therefore I set the system property javax.net.debug=all . Unfortunately, the debug information is not written to the Domino server console and I cannot find it in any of the logs on the server. Can anybody tell me how to get that debug output? 1) In your Notes.ini, create an entry for an options file, i.e. JavaOptionsFile=C:\IBM\Domino9\MyJavaOptions.txt 2) Create this file and add this line -Djavax.net.debug=all 3) Save it & restart the server 4) Open log.nsf to see what happens - the server console is no longer

Included in extensions library (default in Domino 9) there is an 'Object Data Source' feature. Its very handy thing but I cant find any documentation on this. I have a question on 'ignoreRequestParams' property ... what does it mean and how this can be used? By enabling this can URL params be automaticly bound to datasource object properties? The original two data sources (Domino Document and Domino View) both support a behavior that allows URL query string parameters to override property values. By default, the Document data source, for instance, looks for databaseName , formName , and

I'm trying to create an event with a room reservation via the Xpages Calendar Services APIs, with a valid JSON object. Details of the request I am using : URL : [server-path]/mail/administ.nsf/api/calendar/events Operation : POST Headers : Content-Type : application/json JSON Body : { "events": [ { "summary": "Meeting 1 Added via API Call", "location": "Conference Room 2/Site@domain", "description": "Test description", "CalendarDateTime":{ "date":"2014-02-11", "time":"17:00:00", "utc":true }, "start": { "date":"2014-02-11", "time":"17:00:00", "utc":true }, "end": { "date":"2014-02-11", "time":

Here's my set-up: In my XPage, I have an embedded view which opens a document in the adjacent Panel. Clicking the doc link in the view sets the doc's UNID in a viewScope variable, and refreshes the Panel. The UNID variable is used to define the Page's Data Source Document ( doc ). Now in a Button, I want to get a handle to the next document in the view, but when the following SSJS code is run an error occurs at the last line: var v:NotesView = database.getView("ViewByYear"); var curDoc:NotesDocument = doc.getDocument(); // curDoc = v.getFirstDocument(); /* if this line is uncommented the error

to perform a fulltext search users want to simply enter their query into a simple inputText. Then as soon as they hit ENTER the search itself should kick in. Currently we tried to solve it like this: the inputText is bound to a sessionScope variable myQuery the input also has an OpenPage action bound to its onchange event the page that is to be opened contains a viewPanel with a search filter bound to our sessionScope variable, as well as some more FT filtering fields. This works fine in Firefox and Chrome but not in IE ; obviously IE isn't recognizing the ENTER key as an onchange -trigger. So