How to protect Microsoft Word templates for use with ProjectWise?

We have Microsoft Word templates configured to exchange attribute information with ProjectWise using custom document properties and fields within MS Word. The attribute exchange is working fine, however we find that users sometimes remove the fields thereby breaking the attribute exchange within the document.

We have tried to use MS Word's built in 'Restrict Editing' functionality (with Editing Restrictions = 'Read-Only', and also with Editing Restrictions = 'Filling in forms') however this restricts the usage of Track Changes within the documents which we use heavily.

I have also done some trials with inserting the fields into a  Rich Text Content Control (Form Control) and using the protection available within the properties of those controls. Unfortunately the property for 'Contents cannot be edited' prevents the ProjectWise integration from updating the field values. This could be overcome with VBA upon opening the file (unlock>update>re-lock) but then we run into issues around macro security for users and TB Updates and not being able to rendition a .docm file.

Does anyone have any further suggestions to help protect the attribute exchange within a MS Word document without restricting other features?

Parents
  • I've used "Developer" Tab "Design Mode" and grouping the field and text you want to be locked, then turn Design mode off before saving

    There is an issue with tracked changes being left on when advancing a word document through a BS1192 workflow where because the field is locked and tracked changes is trying to record the change in revision it duplicate the field. 

    This leaves the file unlocked for editing but restricts access to deleting fields

    Regards

    Chris


    AECOM Roads UK&I Digital Engineering, Design & Solutions Lead | Sector Information Management Lead

    Principal Engineer – Digital

    OpenRoads Designer 10.10 | MicroStation CE 10.16 | ProjectWise CE 3.4 | ContextCapture | ProjectWise PowerShell 2.0 | Generative Components | OpenBridge Designer 10.10

    Revit 2022 | Civil 3D 2022 | Recap 2022 | Infraworks 2022 | Dynamo | Navisworks Manage

    PowerShell | Visual Studio | Office 365 | Power Automate | Teams | SharePoint | Visio

    Speckle | BIMVision | Revizto | Solibri

Reply
  • I've used "Developer" Tab "Design Mode" and grouping the field and text you want to be locked, then turn Design mode off before saving

    There is an issue with tracked changes being left on when advancing a word document through a BS1192 workflow where because the field is locked and tracked changes is trying to record the change in revision it duplicate the field. 

    This leaves the file unlocked for editing but restricts access to deleting fields

    Regards

    Chris


    AECOM Roads UK&I Digital Engineering, Design & Solutions Lead | Sector Information Management Lead

    Principal Engineer – Digital

    OpenRoads Designer 10.10 | MicroStation CE 10.16 | ProjectWise CE 3.4 | ContextCapture | ProjectWise PowerShell 2.0 | Generative Components | OpenBridge Designer 10.10

    Revit 2022 | Civil 3D 2022 | Recap 2022 | Infraworks 2022 | Dynamo | Navisworks Manage

    PowerShell | Visual Studio | Office 365 | Power Automate | Teams | SharePoint | Visio

    Speckle | BIMVision | Revizto | Solibri

Children