#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

Make new methods in NotesView Class named view.refreshIndex and view.rebuildIndex

As the existing method NotesView.refresh does NOT refreshing the views index but just updates the in-memory object data with the current view index, I´d wish there was a script method which would really refresh/rebuild the views index.


In addition it would be usefull to give the function an optional parameter to either wait for the updall process to finish or to it as an asynchronous updall process, so the script just proceeds but knowing the index update is started (and not only queued!).


This new methiod would be very useful for views with indexes not being updated immediately but hourly or even manually. Before one could work with such a view within a scripting agent, the index needs to be up-to-date!


Of cause the new functions are also needed within the Java pendant.


By the way: The current help entry for the NotesView.Refresh method is very misleading or even wrong!


Mark Reiser

sirius-net GmbH

  • Guest
  • Jan 23 2020
  • Needs Clarification
  • Attach files
  • Guest commented
    29 Jun 10:53am

    @Thomas Hampel

    Can you please "review" that idea´s status?

  • Guest commented
    22 May, 2020 05:54pm

    @Thomas Hampel

    If the user who causes the index update does not have rights, then you can return a Boolean or generate an error.

  • Guest commented
    3 Feb, 2020 02:56pm

    @Thomas - I agree with the other comment, the app developer needs to be in full control of the index. The default refresh timeframe is "Automatic" but if the developer ever decides to use e.g. hourly/daily/etc. then they are doing so for performance reasons. Please be careful about constraining developers on behalf of admins - IBM did this in many occasions and over time it crushed the ability of the platform to organically grow.


    If such an API call does become a major performance issue, then there could be a DB-level property or INI setting added at the server level to disable it by admins.

  • Guest commented
    29 Jan, 2020 12:15pm

    I do not agree. That a view index should not be updated instantly is a architectual decision of the developer for performance purpose. So the developer also needs a "tool" to refresh the view index, when the application logic needs it to be done.

  • Admin
    Thomas Hampel commented
    28 Jan, 2020 08:04am

    The fundamental question is if app developers should be allowed to manage the server behaviour/resource usage. Of course it is reasonable to expect that a view index is up to date, so maybe it is a better approach to change the server behaviour instead of writing code to work around?