Should doc.save work in the postsave event?I am using the post save to do some audit tracking and update a document with a list of the changes made.
Are there any circumstances under which it would be inadvisable to use doc.save in the postsave event?
ie when making changes to a Richtext field, or attachments maybe?
Subject: doc.save in the postsave event
If there’s rich text involved, then a doc.Save from an event – any event – is going to cause problems. It becomes pretty much compulsory to commit to a save & close at that point to avoid a UI overwrite of your back-end changes. You can always re-open the document if the user needs to continue editing.
Subject: Thanks Stan
The problems with it started when we started using “Edit Attachment”.
Does the “Edit Attachment” functionality behave in some “super UI” way that means attachments changed using this functionality do not get saved when a UIdoc.save is done?
Changes to the attachment made by saving it to the hard drive and reattaching are OK in the same app.
Do you have any insight into the difference between these two behaviours?
Thanks again for the feedback. I appreciate it.
Evelyn