Our firm has been trying to setup Sheet Indexing and we are experiencing some issues. When we open the Explorer dialog and go to the Sheet Index Tab the necessary icons are not available.
First image shows our Sheet Index tab. Right-clicking on the 1 icon that is there brings up Refresh (greyed out with a check mark) and Show All. Selecting Show All does nothing. The second shot shows what icons should be available.
A colleague discovered that the Personl.explorer-settings,xml, which is pointed to by a config variable has different values than the one supplied with the training materials. He edited the .xml file and was able to get the icons to appear, however the icons are all greyed out.
He did have post on the ORD forums, but this is a Microstation issue. https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/190394/sheet-index-toolbar-missing-icons
While it is good that he was able to get the icons to appear WE SHOULD NOT NEED TO MODIFY .XML FILES!!!!!
Also, going into the Explorer Settings dialog through the backstage shows only 1 option, to make the Sheet Index Tab visible in Explorer.
This post https://communities.bentley.com/products/betas/openroadsdesignereap/f/openroads-designer-early-access-forum/130787/sheet-index states that you only get the icon when you enable the Edit Sheet Index option. Where do you go to enable the Edit Sheet Index option.
I do have a file where I created a sheet model and I had Add to "Sheet Index" checked on. When I look at the properties of the Sheet Model under the "Sheet" tab "Sheet Index" value shows Not in Sheet Index (greyed out). Also right-clicking on the sheet model in the Models dialog box I see to option relating to Sheet Indexing. 1 is Remove from Sheet Index 2 is Navigate to Sheet Index. Both a greyed out.
I did look at this through an out-of-the-box install of Microstation using the Trianing Material workspace/Workset. Both the Training & my customized configurations for the variable MS_EXPLORER_SETTINGS are pointing to the same .xml file (this would be the one a colleague modified on his PC), but the Sheet Indexing icons appear in the Training workspace.
So is this controlled by a .dgnlib somewhere? I am at a loss trying to track this problem down.
Microstation CONNECT Edition Update 13 - Version 10.13.01.01
As I continue to work on this issue I may have come to the conclusion that this is a ProjectWise issue. I do have some Workspaces/Worksets outside of ProjectWise for some legacy projects that were started in v8i. We decided to use CONNECT for drafting so users could become accustom to the new software format. I opened those files and I see that the Sheet Indexing seems to be functioning.
I am going to switch over to the ProjectWise forum for this issue as that seems to be the root now.
Power InRoads v8i V08.11.07.615
Microstation CONNECT U13 10.13.01.01
ORD CONNECT 2019 Release 2 U7 10.07.03.18
I have been looking at this as well. I found the solution for me in a microstation forum post:
The easiest way to fix this is to delete the existing .dgnws file. It will automatically be recreated with the proper internal name the next time the software is opened. You can find this file in the folder C:\ProgramData\Bentley\OpenRoads Designer CONNECT 10.00.01\Configuration\WorkSpaces\OpenRoads - Metric\Worksets\.
worked for me at least. The problem seems to be a mismatch between the work-set name and sheet index name
Thanks for the reply. I tried your suggestion, but it did not work. If I delete my .dgnws file & open a file the same .dgnws file loads. My configuration points to the correct PW location, but a new one is not created. I've also deleted all of my local files with the same result.
At the risk of stating the obvious, is a restart required to generate a new dgnws file?
Does the index name match your current workset name?
A PC restart?
After deleting the .dgnws file I did restart Microstation. Maybe this would be recreated outside of ProjectWise?
The name of the .dgnws file does match the name of my project configuration (Design.cfg & Design.dgnws). However, the sheet index header shows PennDOT_Design. I have no idea where it picks up that name. We had someone from Bentley set up our PW enviroment. The workspace files were established outside of PW by the DOT. I am not sure what process they used to populate PW, but I am pretty sure they used the import function.
I believe the .dgnws file either became corrupted or maybe it was renamed at some point. I did open Microstation outside of PW and created a secondary workset where I created a new Design.cfg & a new Design.dgnws file. I renamed my original .dgnws file and used my new Design.dgnws file and everything seems to work although I reset the original .dgnws file.
I know that the .dgnws file stores the sheet index information and linksets. Is there anything else that is stored in there. Am I able to replace the original .dgnws file with my new one without breaking anything else?
How are you making the Workset? There seems to be a connection made from the workset template used and the name given in the creation step. We've also learned the directory location of the .dgnws needs to have modify access to prevent the graying out.
Normally I would create the workset by using the drop down menus within Microstation CONNECT open screen. This particular .dgnws file was not created by my firm. We downloaded the DOT workspace. I tracked the problem down to the original .dgnws file. My suspicion is that they created this file properly, but the original workset was named PennDOT_Design. This file was then just renamed to Design. I am sure that they had no idea what this file was used for. This was the case for us. The DOT is also new to CONNECT.
I did find a solution. I created a new workset named Design and copied that .dgnws file into ProjectWise and all seems to be working well.
I am also an administrator on PW so I have read/write access to everything. As stated in other replies here, I was able to create an entirely new workset and the sheet indexing was working. We did not want to be forced to create a new workset and then manually apply that new workset to all of our files.
It is definitely an internal file name of the .dgnws file causing the issue. I verified this by opening the .dgnws file and going to file properties. In there is shows the workset as PennDOT_Design. This field is grayed out so you cannot change it. There is also a Workspace field. However, if you change the workspace field to be undefined the software seems to view that as a standard .dgn file. The workspace option is removed from the properties field in that file.
So I have the work around. I think creating the new Design.dgnws file outside of PW works. I just do not know if it affects anything other than LinkSets & Sheet Indexing.
It must be a PW issue. I setup the PennDOT workspace on our server (not in PW). With that said, I was able to use the PennDOT workspace structure in our core FDOT custom config server/.../Workspaces directory. Worksets are set to the same Workspace folder under Worksets... (as you may know this can be changed via the MY_WORKSETS_LOCATION var). I created a PennDOT_WORKSET_TEMPLATE and made my setup/server changes in that cfg file. Close ORD and Once you open ORD again, click "Create Workset" and select the PennDOT_WORKSET_TEMPLATE, enter new workset name in name field and that "name" will become integrated into the newly created sheet index, workset cfg and dgnws ( and associated folder). In this case, there was not an original .dgnws file. The PennDOT_5.0.9_19R2 workspace I downloaded on Jan 8th did not contain any worksets, so there's a chance whatever they added to the workspace may have complicated the process.
It must be PW.
Everything is not working correctly by creating the new Design.dgnws file outside of PW. It appeared that it was working, but when I try to add sheets to the sheet index it states that the files are not part of the current workset.
can you take the new dgnws file created outside PW and replace the one thats in PW?
That's what I did. I get the message that the selected files are not part of the active workset when trying to add them to sheet index.