We do so here to append the revision parameter automatically. It’s not a simple process. We use a series of nested mapkeys along with nested batch files to process the output.
Our method goes something like this:
- Create a temporary folder on the server. (This provides a consistent path for working with the exported files. It also helps insure that files don't get overwritten.)
- Output the file in the desired format to the temporary folder.
- Save the parameter information for the file to the temporary folder as a text file (not HTML) using a consistent file name.
- Use a batch file to parse the text file for the desired parameter (‘revision’ on our case) and extract that parameter value to a variable.
- Use a batch file to find the name of the file that was exported and extract that to a variable.
- Use a batch file to create an final output folder named with the date and the file type (111027_IGES for example).
- Use a batch file to rename the output file <filename>_<revision>.<type> and move it into the final output folder
- Use a batch file to clean up all the temp files and folders
I use a series of nested batch files and nested mapkeys that let me export a variety of formats - PDF, IGES, STEP, STL, etc. There are a lot of free batch file resources out there to help you create what you need.
My batch files have grown and gotten more sophisticated over time, to the point where it’s hard to share because they are so interrelated. One thing that makes it tough is that I use a ‘set_vars’ batch file to set a bunch of variables that are used downstream. I also have to accommodate typically 3 versions of Pro/E at a time and work with a variety of export formats and exporting with and without the rev parameter. That said, here are some snippets that may help you.
This captures the file name of the exported file type (%long_type%). Assumes only one file is present in the directory.
rem ** generate list of %long_type% files
dir /b *.%type% > dir.txt
rem ** extract the %long_type% file name
findstr ".%type%" dir.txt > %type%.txt
for /F "tokens=1 delims=. " %%i in (%type%.txt) do set FILENAME=%%~ni
del dir.txt
del %type%.txt
This creates a folder based on the file type and the date:
rem ** create destination folder
date /t > fulldate.txt
for /F "tokens=2 delims= " %%i in (fulldate.txt) do set today=%%i
set today > date.txt
for /F "tokens=2 delims=/=" %%i in (date.txt) do set MONTH=%%~i
for /F "tokens=3 delims=/=" %%i in (date.txt) do set DAY=%%~i
for /F "tokens=4 delims=/=" %%i in (date.txt) do set YEAR=%%~i
SET destination_folder=%long_type%_%YEAR:~-2%%MONTH%%DAY%
md %destination_folder%
del fulldate.txt
del date.txt
This will find the revision in a text based (not HTML) parameter output file and rename the exported file:
rem ** extract the revision
findstr "REVISION" dc_param_temp.txt.1 > rev.txt
for /F "tokens=3 delims= " %%i in (rev.txt) do set REVISION=%%~i
del rev.txt
rem ** rename %long_type% file to include revision
rename %FILENAME%.%type% %FILENAME%_%REVISION%.%type%
The ‘tokens’ value above may need to be 2. With 2001 it was 2 and with Wildfire it was 3, I think, but I may have that backwards. I had to add a section in my files to determine which version it came from and it’s still there even though we stopped using 2001 years ago. I didn’t document which was which, unfortunately.
That should help you out. Keep in mind there are likely variables in there that won’t work in your situation, be on the lookout for those.
Good luck!
--
Doug Schaefer | Experienced Mechanical Design Engineer
LinkedIn
