Why can the user enter some non-number characters in a number field? Why isn´t this blocked just in time? It should be possible
Only when he save the form/document he will get a "cannot convert text to number" error message and this produces some user-frustrations.
What I would ...
I would like all fields to have the onChange event implemented, perhaps excluding rich text fields. And I would like that event to fire right after a change in the field value, not when the field looses focus. By that time it is sometimes too late to do anything about ...
Allow selecting a number of fields and then allow editing all those properties that can be common to all those fields together. Some properties I would like to be able to set on multiple fields will include style properties, formatting, multi-value handling, etc...
In workflow applications we often need to save Fully Qualified names in Readers/Authors/Names type fields in order to reduce name ambiguities e.g. “Joe User/dev/demo” or “Joe User/adm/demo” however for display purposes people like to have “Joe User” only instead of complete fully qualified ...
When a summary field exceeds 32K, all hell breaks loose and programmatic remedy is almost impossible. Any LotusScript operation on such fields fail (ie cannot even remove!).
Replication also fails. NO REMEDY POSSIBLE :( I believe even formula-based replication fails, as the SELECT throws an error.
This sort of thing happens ...
can we have an visual indicator on a field in designer which shows us HOW the data for a field is being generated?
something like E for editable, CFD for computed for display, CWC for computed when composed etcetera.
nowadays we have an indicator which shows us what ...
I guess this is more a fix than an idea, but never late then never:
If I select a color for a checkbox field it is not supported (mines become standard black)
Bold and italic is supported...
When a user is using a web app (or any app for that matter), and he/she moves from one field to another (e.g. by using the tab-key) the content of the field that gets the focus, is usually selected. The moment the users starts typing, that content is overwritten.
Support of groupboxes. There are workarounds using layers but yeah these are workarounds...
Lotus Notes designer is good .. you can get stuff done way quicker due to all the options you have .. often just a check box. The down side is that sometimes you lose that bit of flexibility.
Like when you want to refresh fields on keyword change .. ...
This would be great for updating fields. One could write:
@SetField("strStreetname"; @GetDocField( contact_replicaid; contact_unid; "strStreetName"));
Did you ever open a document and wonder where a specific field is used? Of course, you can open a form in Designer, but then you don't see the value. So you'll have to go back to the client, look at that spot where you find your field and see ...
would make it much easier to add multi value fields on an XPage...
If I create a form that is going to be used just as a data source for XPages I find it a bit stupid to create all the fields, field by field.
a wizard to add more than one field after each other would be nice...
A field that is computed for display and located in the header seems not to be available in the rest (body) of the form.
Computed fields however are.
Ability to stop searching a form for a word, this will be time saving especially when the form contains big number of fields and you have by mistake chosen to search 'Scope: All Objects"
This would be a field setting. I don't see a way to implement this with scripting, so I would like to see it implemented in the replication procedure.
Suppose John adds $1.00 to the "totalamount" field and Susan adds $3.00 to the same "totalamount" field. When replicating this would ...