#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

Add "force update" option to @GetProfileField / profile documents

Profile documents are a great way to store basic configurations or even user based configurations for an application.

The documents seem to be cached for better performance. This is also great.

But this is also sometimes an issue. When you make a change in such a document and you leave the document open after saving your changes, a @GetProfileField ( and also LS methods ) do not return the changed value. The cached value is returned instead.

Sometimes, you have to close the entire Notes client for the changes to take effect. 

I would like to see an additional / optional parameter in @GetProfileField to force an update of the cached values ( like the NOCACHE option in @dblookup )

  • Guest
  • Jul 18 2018
  • Needs review
  • Attach files
  • Guest commented
    22 Aug, 2018 02:22pm

    This would be great to see also in XPages equivalents, as the only approach otherwise is to retrieve the entire collection of Profiles, which isn't cached, and iterate through until you find the specific profile you need to be "fresh" -- I like the caching model but definitely, more control is needed to bypass cache without resorting to iterating...