# vs $ in the computed expressions in the xpages

In the xml code of the xpages the computed expressions begin with the character “#” or with the character “$”, ie they are one of the following types:

  • value=”#{[language]:[expression]}”
  • value=”${[language]:[expression]}”

where [language] is the name of the language, for example javascript and [expression] is the expression to compute.

The question is “what is the difference between the two cases?”. Continue reading “# vs $ in the computed expressions in the xpages”

How to access to a control connected to a lotus field using javascript

In this post I test how to access via javascript to the following controls connected to a lotus field:

  • Edit Box: a control for entering a single line of data
  • Hidden Input: a control for hiding data to the user

A Hidden Input control is not such as an Edit Box control with “Visible” unchecked (or with property rendered set to False) because an invisible Edit Box control is not rendered in the page, not even in the html code with an attribute type=”hidden”. Continue reading “How to access to a control connected to a lotus field using javascript”

The Form Layout Column control of the Extension Library

The Form Layout Column control allow you to place the various controls (such as Form Layout Row) on multiple columns.
In the post The Form Table and Form Layout Row controls of the Extension Library I built a xpage with two Form Layout Row controls at different lines, using two Column Layout Form controls you can place the two Form Layout Row on two different columns on the same line. Continue reading “The Form Layout Column control of the Extension Library”

Hidden fields in a lotus form open with a browser

In a lotus form you can hide the fields enabling the check box “Hide paragraph from Web browser” in the window of the properties of the field but in this way the field is not generated as a hidden field, i.e. a html tag input with attribute type=”hidden” is not generated and you can’t access to its value from a browser, for example using javascript.
This is a different behavior from that one using a lotus client where you can still access to the hidden fields using lotusscript and formula language. Continue reading “Hidden fields in a lotus form open with a browser”

How to fix a corrupted view of a lotus database

I found this command to use on the console of the domino server to rebuild a specific corrupted view in a lotus database without rebuilding all the views of the database:

lo updall -R [database] -T [view]

where [database] is the path to the database and [view] is the name of the view.

Getting the current document from a button in an embedded editor

Consider the following scenario:
a lotus form containing an embedded view and an embedded editor, the 2 embedded controls are linked together according to targeting by linking an embedded editor to an embedded view.
The embedded editor contains a button that tries to get the current document (often called uidoc) with the code:

but this code returns the NotesUIDocument of the document linked to the embedded editor and not the NotesUIDocument linked to the main document. Continue reading “Getting the current document from a button in an embedded editor”