Hi Fer, thanks for your input! I've started editing this reply at least four times in the past days [quote userid="1317538" url="~/products/plant/f/autoplant-axsys-openplant-plantwise-forum/256915/register-design-file-dialog-when-publishing-imodels-interrupting-macro-execution/804683"]Register the files manually in the rcmproject.xml file. You can manually enter a GUID code for each file. The caveat here is that it will have an issue if the DGN files have been registered when checked out from ProjectWise. [/quote] I've made a python script that created all the entries in the rcmProject.xml file in the root of the local export folder, with pregenerated GUIDs. But it didn't fix the issue. For a small number of models it worked, but for the majority of them the Register Design File dialog kept popping up on every model open, and the model entry being added again in the xml file with a warning that there was a duplicated entry. [quote userid="1317538" url="~/products/plant/f/autoplant-axsys-openplant-plantwise-forum/256915/register-design-file-dialog-when-publishing-imodels-interrupting-macro-execution/804683"]You could try checking out the DGN from ProjectWise to see if the Register Design File dialog will still pop-up, considering they were previously registered before. [/quote] Regarding the "Checking out" the files before running the macro, that didn't work, but doing that I realized that t he "Project" rcmProject.xml file was in the Designer's wip, for both network and ProjectWise configurations, and it's not being used by BRCM I'm not sure if it needs to be like the following, but we don't have a DGN folder in the Project root folder (Workset), neither the rcmProject.xml file itself there. That happens both for the network configuration and also the Projectwise's managed configuration. As I had no success with our support team relocating the rcmProject.xml file or fixing configuration files that may be misconfigured, I've finally "patched" the issue with an external method. I've written a Python script that is called from the vba macro, which monitors the presence of the Register Design File dialog window, and if it finds it, it activates it, and just accept the default option. For the time being, we couldn't find any issue with that approach. Thanks again and sorry for taking this long to reply
↧
