Users are often confused when they see the 'Keyword selection' dialogbox, used when a field is of type 'Dialog list'.
I would love to define the prompts/title/labels used in that dialogbox myself.
Also for multilingual database this could prove useful.
Building a custom dialogbox is not an option, because e.g. ...
I think the precedent has been set (with Shared Actions and Shared Columns); how about Shared Selection Formulas? I think they are a logical extension of what we already have. Additionally, I'd like to see Shared Form Formulas.
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.
Sometimes it would be nice, we could show documents from 2 ore more databases in one view.
An example is the display of appointments from a CRM database and the appointments from the
calender inside the users mail database in one (calender)view.
A possible solution to overcoming the problems associated with embedded views and not being able to sort the columns etc could be to set the selection criteria for the view at runtime - e.g. as a property of the embedded View object and not at the View level itself. This would take precedence ...
this would rather fit into various idea spaces since it touches the storage system of views. Within almost every database I know, many views have the same selection formula as other views, resulting in the same collection of documents. As far as I know these collections are all evaluated and ...
It would be nice to have the option to highlight a document in a view and have the highlight move to that document when you switch to another view in that database. Sometimes it is necessary to see a document in a different context. For example, from a view containing ...