Hi, everybody!
I'm using GWP for publishing a DGN file with many of associated files.
For that I'm configuring the auotomated idpr convertion in GWP Administation.
GWP follows the changes only in one file, the one that has been published, but it does
not follows the changes in the associated files.
This way having the associated files becomes useless.
I can press "Start process" in GWP Administration UI to update automated idpr
file if any changes was made in associated files.
Does anybody know, how to make GWP to track changes in associated DGN files,
or any way to programmatically "Start process" to reconvert automated idpr file.
Thank you. Sergey.
As well as Nelson's comments. You may want to consider creating a 'layer' for each of the reference attachments, so that the GWP output mimics the reference attachment schema. This also would have to be done just once, but may give you more flexibility in the usage of those various files.
Nelson, Jerry, thank you for responces.
Of course I mean "references", and of course I would like to do a change request. What should I do for it?
The solution "creating a 'layer' for each of the reference attachments" takes his place, but in this case it's too difficult to publish all references separately (look at the picture for example, this is a most simple case, is other cases we have a hundreds of references).
Left folder is a root for the project, next level of folders is for departments, which takes a part in the project. Next levels may be very complex.
On a third level of the project folder structure we have a master files, which collects all data and makes a big picture.
Master files are not changed often, they are used for printing.
We want to do a more automatic system, and for our case we can assume another solution:
1) Publish a master file as an automated idpr, which includes all other files needed for particular case.
2) Open master file once a day, using Bentley SDK, and resave it (change date for the file)
3) GWP tracks changes in master file by date (as I assume), so all changes in references will be taken into account.
How do you think, is this solutions have chance to live?
Just 'touch' the main file. You can set up a Windows AT command , and schedule it to run ince a day. GWP should take care of the rest.
Jerry just 'read my mind', although 12 hours ahead of me.
Sergey, I see no particular reason that the nested reference attachments should be a problem. It should work.
Just ensure that your attachments are set to Live Nesting, and with the appropriate depth etc.
With complexity comes the ability to compromise the system. If a problematic file is added at the Nth level of nesting, would it be difficult to troubleshoot?
So also consider backing up your
monday.dgn
tuesday,.dgn
etc.
* Jerry's command/batch file might also so the backup/renaming for you.
Likewise, always consider backing up production server configuration files. (Pubconfig.xml, ...)
Many thanks! We will try 'touch' file once a day.
Is there any xsd document for PubConfig.xml to extract all published automated iDPR?