#dominoforever | Product Ideas Portal

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

We need more detailed better error reporting when a form/element is opened in a browser and embedded code processes.

Many times a field has an issue with either default or computed field code and we get a Form 500 or some other general error. Just having the error inform as to where the error is in the code such as the field name or the details on what caused the error. Today we can only see the error information by opening the form in notes and it will warn us about the field where the error resides. That becomes difficult for those forms meant for web only viewing/use. By default those will have many problems and issues rendering in the notes client.

  • Guest
  • Oct 15 2020
  • Under Consideration
Domino Designer / Debugger
  • Attach files

Related ideas