Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
I propose changing the subject of the current idea to "Unification of @Picklist and PickListStrings".
By the way, the PickListStrings method has the same disadvantage - it is impossible to specify the server from which to open the address book.
It would also be great to be able to specify the optional database parameter in both functions to open a dialog from your own directories, and not from the address book.
The request subject is incorrect. @Picklist should not be performed using Evaluate!
There are disadvantages to both functions. And improvements to both functions are long overdue.
The disadvantage of the PickListStrings method is that you cannot pass an array of values that you already have. And this is very inconvenient! An additional optional parameter is needed to pass an array of existing values.
The disadvantage of the @PickList ([NAME], [ROOM], [RESOURCE]) function is that it displays data from a single (static) address book. We work on different environments simultaneously, in which the contents of address books are very different or completely mismatched. It's also very inconvenient. Adding the optional sever parameter is very necessary for choosing which server to open the address book from.
As a result of this unification, it is expected that PickListStrings and @PickList will work the same. The appearance is needed like @PickList, with a right panel.