We have a ProjectWise Managed Workspace with typical Predefined, Site, Project and User levels defined. We've made a change to the load sequence for MS_CELL < $(ZONE_UTIL)cell/*.cel and MSCELLLIST <$(ZONE_UTIL)cell/*.cel in our test environment that correctly redirected the default Our_Local_Ext folder to Zone_Util_Ext. But when we repeat the process in our production environment we cannot seem to access Doors and Windows, as though the process is going to the wrong configuration file to call the cell folders. I then replaced our custom Zone_Util.cfg file from a backup and purged the workspace from the Local Document Organizer. This seemed to partially work in that we could navigate to the correct cell files, but we still can't access Door or Window cells from their respective placement tools; e.g., as though it was still reading from Our_Local.cfg instead of ZoneUtil.cfg.
For example, here are paths defined in our test environment:TF_EXTENSIONROOT = pw:\\our.company_02.com:pwtest\Documents\Engineering\BIM Standards\Workspace\Extensions\ %include pw:\\our.company_02.com:pwtest\Documents\Engineering\BIM Standards\Workspace\Extensions\Zone_Util_Ext\Zone_Util.cfg And our Production environment:TF_EXTENSIONROOT = pw:\\our.company_01.com:pwprod\Documents\Engineering\BIM Standards\Workspace\Extensions\ %include pw:\\our.company_01.com:pwprod\Documents\Engineering\BIM Standards\Workspace\Extensions\Zone_Util_Ext\Zone_Util.cfg
Choose ProjectWise > Project Properties > Workspace tab > Site, and notice that Our_Local_Ext is positioned below Zone_Util_Ext which results in Our_Local_Ext displaying first.
Within the applicable CSB:
Directive%includeType: ProjectWise DocumentValue: pw:\\our.company_01.com:pwprod\Documents\Engineering\BIM Standards\Workspace\Extensions\Zone_Util_Ext\Zone_Util.cfg