The filename already changes when the document name is changed but I need the document name to change when the document name is changed.
I assume I'll need to create a custom module with a post trigger on the Doc code written in C++ and register the module. Then add the dll to everyone's PWE.
Looking for guidance here as I normally write external programs in VB.NET.
Kevin,
Eager to understand what your use cases might be.
If the intended use is to align document name/filename on a change to document code, how will that change be reflected on versions other than the active version? Metadata in earlier versions (including the document code) are read only.
Regards, David
David,
Document Name and Filename needs to match Document Code. Currently users are changing Document Name only and causing issues.
Not concerned about previous versions, they can stay as is.
That old chestnut..... I suspect many of us have been challenged by that user behavior. To me, it highlights the difficulties in appreciating there are potentially 3 opportunities to misalign name information in PW - Doc Code, Doc Name and File Name.
Our experiences with renaming documents and changing the document code to suit (or vice versa) often leaves the original document code embedded in earlier (read only) versions, rendering reuse of the original doc code (almost) impossible. Purists would say that the document should be withdrawn, however this is not always a practical solution, particularly during design phases.
Does anyone in the Community have any ideas on how to efficiently resolve this challenge?
Just tested this and can see that you're right. This a real problem!
Looks like we'll just delete the documents with the old doc codes. What was your solution?
Can suggest two approaches - neither of which are ideal.
Option 2 is a laborious, error prone process. You still lose audit trail and cannot easily re-associate the correct versions of references to versions of their master documents. (other than the active version)
IMHO, the whole process of Doccode generation/manipulation and the unique dependence to environments in PW is in serious need of a refresh. Its one of the best quality based features in PW, however its one of the most onerous to manage at both project and Enterprise levels.