I am seeing very weird behavior with a Profile Document.
I have an outline entry to edit the document that is coded like this:
@Command( [EditProfile] ; “DataBase Settings”)
The document is named “Database Setting/Database Settings”. Four or five people have access to it.
User A edits and saves the document and makes a change to a field. Then user B edits the document but they don’t see the change.
When I open the document I do not see the change, but I DO see the change when looking at the backend document using NoteMan.
I do not know why this is happening, and it is driving us crazy. Does it have something to do with Profile Documents caching?
Any help would be greatly appreciated.
Bryan
Subject: Profile documents
This is working as designed I reckon. Profile documents are cached on a workstation for the duration of the session (as long as the person has the application open). So once a user has the app open it doesn’t matter if someone else edits it they’ll see the version they cached when they opened the app.
I think the only use for profile documents is for personalised profiles, not general ones. Use a normal doc in this case
Subject: Forcing profile cache refresh
Dan is right about how profiles behave, but if you want to provide an editing interface that gives the authorized editors up to date information, use the Delete statement from LotusScript to delete the profile from memory. So:
dim docPro as notesdocument
set docPro = db.getprofiledocument(“whatever”)
delete docPro
uiws.EditProfile “whatever”
Please note the profile is also cached for end users, so a design where you keep changing the profile frequently will not work. Shared profiles are appropriate for information that’s fairly static.