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.
Hello Sergey,
By 'Associated', I believe that we are intending 'Reference’ files.
Of course, a reference file structure created within MicroStation can be quite complex and possibly replete with missing or otherwise invalid path references. (perhaps the GWP process does not have access or permissions to certain paths, etc). So, accounting for these aspects can be difficult. Nonetheless, we can consider filing a change request for this functionality, but it may come with some limitations (perhaps a nesting depth limitation, a 'what to do when we cannot resolve a reference' timeout limitation, etc.). If you would like a change request in that light, please let us know your desires regarding those scenarios.
As a stop-gap measure, you may run the iDPRcnv.exe commands via a scheduled batch file. This is mentioned within the prepublishing documentation:
docs.bentley.com/.../GUID-105B1F4D-99D6-4961-96E6-4EB017A76208.html
Consider also that perhaps a scenario without the use of the master/reference relationship may be suitable in your case, if you do not rely on functionality specific to the reference attachment.
i.e. As “all roads lead to” the same iDPR file ultimately, could the reference files be added directly as Automated iDPR Input files, thus making use of the inherent change tracking?