Can anyone give a definitive answer - many questions posted in the forum, but never answered.
I am trying to use the design refresh to update values in a database profile document in all databases that inherit from a template. It should work, if Help can be trusted.
Scenario is this. Template contains one database profile document called Defaults. It is created as a normal form, unticked “Include in menu” and “Include in search builder”. Template database has ticked “Copy profile documents with design”. But after I do design refresh, there’s no profile document in the target.
Subject: RE: pushing profile documents during design refresh
The help says (emphasis added):
Copy profile documents with design - Databases created with this template also get any profile documents within the template.
This only talks about database creation – it says nothing about design refresh. The whole point of profile documents is to let specially authorized users modify them to change the operation of their copy of the application. So you don’t want to overwrite those documents during a design refresh.
Admittedly, it might make sense to create the profile document during design refresh if it doesn’t exist already. However, since this doesn’t happen (and was never the intended functionality), you should consider workarounds.
You might use LotusScript in an event that executes when the database opens, to check for the existence of the profile (GetProfileDocCollection method), and if not, create it with default values (or locate the prototype in the template and copy it over).
Or, simpler, use GetProfileDocument and see whether it contains non-blank values in certain items, and if so, assign the default values.
Subject: RE: pushing profile documents during design refresh
Thanks Andre - next time I won’t take off my readers
However, it also says " Databases that inherit their designs from master templates receive the latest changes through a nightly server task." I am not complaining so much that the profile document is missing, but that even if it’s there (by following your rule), changes in the template’s profile document do NOT get pushed out to the inheriting database. At least Help could warn us that the refresh doesn’t include profile content.
Subject: RE: pushing profile documents during design refresh
As always, if you see a way we can make the help information more complete, I encourage you to click the feedback link on the help page and fill in the suggestion form. I do this myself, so you’re really not gaining anything by telling me. The feedback is processed by an intelligent person who takes action – that’s why I feel no need to try to bypass the established process.
