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
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.
Very frustrating!
Microstation CONNECT - 10.17.2.61
ORD - 2021 R1 10.10.1.3
ORD 2022 R1.1 - 10.11.3.2
ORD 2022 R3 - 10.12.2.4
Microstation v8i SS 10 - 08.11.09.919
Power InRoads v8i - 08.11.09.615
ProjectWise - 10.0.3.453
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.
So it turns out that the issue is not with PW. I went back to my workspace outside of PW. I was opening the Desin.dgnws file I created and received an alert that the file was looking for the PaDOT workspace. That's when the light bulb came on and I relized the workspace name was mis-matched. In PW our workspace is PennDOT.
This turned out to be a simple fix. I opened the Design.dgnws file with Microstation went to the backstage and selected Properties. This brings up a dialog box with a Workset Properties area. Within that area is a Workspace field that can be edited. I just replaced PaDOT with PennDOT. Their is also a field for the Workset name also, but that is cannot be edited.
I am now able to open the file that I was not able to add the sheets to the index and add the sheets. I also added sheets from another file without issue.
Shawn Cooke said:The PennDOT_5.0.9_19R2 workspace
The workspace version I had was 4.5! Maybe the workspace had been recreated for newer versions and did not lose integrity.
I had the same issues and was able to resolve this in two ways:
Provide full network access rights to the WorkSets folder (which I store on a separate network drive from the project files)
Delete any DGNWS files that were not working properly and allow new ones to be recreated (may lose data stored in them if being used).
I had a DGNWS WorkSet that I had used for testing purposes that had been compromised by my repeated file renaming and moving of folders while learning how these work. I deleted the file and started a new one and it was fine. I do have admin rights to the folder and was even locked out of editing the sheet index without deleting the DGNWS file and allowing a new one to be created. Once I did that it worked fine.