Revision number in PDF file name

ok  but since we dont  hae that  feature in utn natively  how about a  differnt  work flow?

What about  when you start every file it has the  format  name_<rev letter>.dgn ie  12345_caltex_A.dgn?

Then when you batch print  you can allow the  fullname  to be the pdf name..

Now  i assum you have  many  files already  that  dont have this  but  if you have  paper copies or  lists  you can use  a  great little  free ware  tool called bulk rename  utility   it will alow you to append the _REV name file letter  to each file name  with a  drag  fill series to a list  of  files it has a  sort of windows explorer gui to it  but  lets you do bulk rename not just  one at a time  it also can ,append  ,pre append , inserts and  renumber .. if your not  sure what  every file  should be  renamed you can   just open the  pdfs by swaping out to open the  pdfs to check..and  return toggle to the  utility..

I renamed/renumbered several hundred files this way  in less than 15 min  and my  pc  is very  slow..

I like the  preview  feature  of  current  name  of  file beside end result  of file name  before you say  ok go and rename  the  lot..

as you can tell I like this tool a lot..

take a  look at  it at 

http://www.bulkrenameutility.co.uk/Main_Intro.php

there are  lots  of  pics about what  it can do one you  have  it you'll rave on too and its totally  free  even for commercial use..

<Phil Chouinard> wrote in message news:91060@communities.bentley.com...

What you speak of is all true -- having been involved with developing, implementing, and "enforcing" standards, it sounds a lot easier than it is. I once heard a statement about standards, they are like toothbrushes... everyone has one, but most do not want to use anyone else's :) Seriously, we are all about standards -- we are involved with a number of them and encourage their use. We have even implemented tools in MicroStation to help in that cause (see this blog post for more regarding that).

Another "twist" in all this is the revision "format" itself. If you go to Help > Contents and search for MS_DESIGN_HISTORY_REVISION_NUMBER_FORMAT, I believe you will see what I mean.

PS - there are other ways to "track" revisions, too, that I did not specify previously. The V8 DGN file has a revision file property and ProjectWise is quite customizable in that aspect.

---

http://communities.bentley.com/Products/MicroStation/MicroStation_-_all_pre-V8_versions/MicroStation_-_all_pre-V8_versions_Printing/f/165/t/41063.aspx#91060

Thank you all for your kind help.

Phil, you mentioned that "Tags" can be used...Could you please provide extra details on how we can use tags and tags sets in this mathod?

We use tags in our DGN's for other purposes, but how can we use it (As a revision number) in the PDF file name?

What code (if this is how to implement this idea) can be used?

TIA

What you speak of is all true -- having been involved with developing, implementing, and "enforcing" standards, it sounds a lot easier than it is. I once heard a statement about standards, they are like toothbrushes... everyone has one, but most do not want to use anyone else's :) Seriously, we are all about standards -- we are involved with a number of them and encourage their use. We have even implemented tools in MicroStation to help in that cause (see this blog post for more regarding that).

Another "twist" in all this is the revision "format" itself. If you go to Help > Contents and search for MS_DESIGN_HISTORY_REVISION_NUMBER_FORMAT, I believe you will see what I mean.

PS - there are other ways to "track" revisions, too, that I did not specify previously. The V8 DGN file has a revision file property and ProjectWise is quite customizable in that aspect.

Phil,

I agree that in detail all standards vary. This is why I referred to ISO 13567. Most CAD standards I know rely on this world wide standard, so this is a good starting point. The point is, that ISO 13567 describes a faceted classification. The variation in the CAD standards is 1. which facets are used 2. which notation is derived from the choosen facets.

Therefore a tool relying on the facets of ISO 13567 could easily manage inumerable different file naming standards when the tables for each facet are configurable by the user (administrator). This is what ISO 13567 for good or for bad allows.

I agree that there are various ways to implement such functionality. However IMHO the range of obvious solutions is not as broad as you indicated.

Obiviously tags and fields have a great potentential to represent the input, because they have a history of serving such purposes.

Not to create metadata for the designfile for document management purposes out of the necessary user input would waste a great chance. A filename has to be specified, but most users miss the opportunity to facilitate document retrieval by creating a set of metadata. This could be done on the fly by a tool like that.