Share via

Office 365 Document Naming convention

Anonymous
2022-05-06T09:20:29+00:00

Hi, I am trying to create something I used a while ago, and that is, whenever someone creates a new doc, sht, ppt etc a box appears and mandates that the user completes certain mandatory fields, ie a predefined document naming convention.

So I would select Word and then new document, this box will appear and mandate that I initially provide;

yyyymmdd

Time and time zone (optional)

file_name (with underscores between the words in the file name)

Document status (Draft, Final)

Version number (v1.0)

Originated Department of Position (optional HR, Contracts, Sales, or CEO, CIO)

Protective Marting( O, C, S - Official, Confidential or Secret)

Descriptor (optional MGT, POL, TPT)

File Reference (01_01_03)

Each element would be separated by a hyphen and where optional fields are not required no spaces are left.

I guess my question is, is there a way in 365 for this to work with Outlook, Word, Excel, PPT etc

Many thank

Andy

Microsoft 365 and Office | Word | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2022-05-06T10:52:38+00:00

    Sounds like a good idea. I like naming standards.

    .

    I have not seen one enforced. I suppose it may be possible through a "policy", but I have not seen it imposed.

    .

    Another option would be to create a macro that overrides the SAVE command. The VBA would present input boxes for each of the required parameters.

    .

    It may also be possible through PowerShell. I know PS has lots of functionality, and lots of extensions. I have no specific idea if it is possible. You should ask a PowerShell expert.

    As well as googling, you could try searching through the PowerShell "Gallery". It is collection of thousands of PS related items you can download free. Some are "official" MS contributions, some are user contributions of scripts. A very brief scan did not find anything, but is worth a deeper look.

    https://www.powershellgallery.com/packages

    Was this answer helpful?

    0 comments No comments