I’d like to create a page or form as a holder for values that would be applied though out the database.and Example would be sales tax.
Lets a assume that I have a collection of documents that rely on the same value, and that periodically I want to change that value without changing the hard code of the form.
Can I create a page with the stored values as fields?
Or do I create a form with the intention of only using one document.
Subject: Best practices question on global variables
That is THE canonical application for a Profile Document – a single document used to store configuration information. Profile Documents are cached, meaning that the “cost” of looking up to them is minimal, and there can only be one Profile Document at a time for any given purpose. Designer Help can give you more information.
Subject: RE: Best practices question on global variables
Perfect.I figured there would be some mechanism.
I just didn’t know what to call it in the search.
Jim
Subject: RE: Best practices question on global variables
If you use profile documents just be aware that they are loaded into memory when the DB is first accessed. If you have any scheduled agents running on the server that get values from a profile document, they won’t pick up any changes to the profile document unless you do dbcache flush at the server console (or restart the server!)