#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

Lotus Script stack trace function instead of the unsupported Lsi_info(14)

Please add a regular and offical function to get a Lotus Script stack trace instead of the buggy and unsupported function  Lsi_info(14).


Mark Reiser, sirius-net GmbH


LotusScript, Script, LS, LSI, Lsi_info

  • Guest
  • Jul 25 2018
  • Under Consideration
  • Attach files
  • Guest commented
    8 Aug, 2019 11:53am

    In LSI_Info(14) the stack contains modul name placeholders ( i.e. *DE3AA18) . Would be really great if it would be replaced by the real modul name.

  • Admin
    Thomas Hampel commented
    27 Oct, 2018 09:36am

    Moving idea to product : Domino Designer

  • Guest commented
    7 Oct, 2018 03:35pm

    officiallising lsi_info(2) would be useful too !

  • Guest commented
    24 Aug, 2018 07:20am

    One of most important information for errors tracking is the current class name. We can use Lsi_info to get current method name but we couldn't see it's class name.

    Obviously we can get Typename(Me). But if we put this code in the "Code template" we will get a error in standalone functions and procedures.