CE- Sheet Index

RE: CE- Sheet Index

Jeff Purl — Tue, 07 Feb 2023 20:31:04 GMT

RE: CE- Sheet Index

Rod Wing — Thu, 05 Nov 2020 20:08:15 GMT

I get the same results as you do just by renaming the WorkSet

https://communities.bentley.com/products/administration/f/product-administration-forum/204959/ms-ce-u14---remapping-the-sheet-index

You will see in that thread I logged a ticket with Bentley and they have filed a Defect on this.

RE: CE- Sheet Index

Robert Sidman — Thu, 05 Nov 2020 15:52:21 GMT

Without knowing more how you have your Workspaces configured, It seems to me that any discipline that opens a file within a project WorkSet will be using the same .dgnws file. The WorkSet name is linked to only one .dgnws file. I am not sure if there is a way for multiple .dgnws files under each WorkSet or not. I would contact Bentley about that.

RE: CE- Sheet Index

Shawn Cooke — Thu, 05 Nov 2020 15:26:08 GMT

Every discipline appears to use the same dgnws file for a given project. Yes, each project has its own workset.

RE: CE- Sheet Index

Robert Sidman — Thu, 05 Nov 2020 15:18:19 GMT

Do you have separate WorkSets for each project?

RE: CE- Sheet Index

Shawn Cooke — Thu, 05 Nov 2020 15:15:35 GMT

Every discipline appears to use the same .dgnws file for the project. Has anyone ran across an issue with this? There may be times when each are working on sheet development around the same time.

RE: CE- Sheet Index

Robert Sidman — Thu, 05 Nov 2020 15:06:07 GMT

For what it is worth I am working with the PennDOT configuration as well. It did not seem to have anything to do with their configuration. At least on my end.

RE: CE- Sheet Index

Robert Sidman — Thu, 05 Nov 2020 15:04:50 GMT

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.

RE: CE- Sheet Index

mwlong — Wed, 05 Feb 2020 15:56:23 GMT

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.

[quote userid="1021592" url="~/products/microstation/f/microstation-forum/190917/ce--sheet-index/567273"]The PennDOT_5.0.9_19R2 workspace[/quote]

The workspace version I had was 4.5! Maybe the workspace had been recreated for newer versions and did not lose integrity.

RE: CE- Sheet Index

mwlong — Wed, 05 Feb 2020 12:41:20 GMT

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.

RE: CE- Sheet Index

Mike Thompson — Tue, 04 Feb 2020 19:55:22 GMT

can you take the new dgnws file created outside PW and replace the one thats in PW?

RE: CE- Sheet Index

mwlong — Tue, 04 Feb 2020 18:37:02 GMT

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!

RE: CE- Sheet Index

Shawn Cooke — Tue, 04 Feb 2020 17:24:45 GMT

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.

RE: CE- Sheet Index

mwlong — Tue, 04 Feb 2020 16:46:37 GMT

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.

RE: CE- Sheet Index

Shawn Cooke — Tue, 04 Feb 2020 15:54:36 GMT

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.

RE: CE- Sheet Index

mwlong — Tue, 04 Feb 2020 13:06:02 GMT

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?

RE: CE- Sheet Index

Mike Thompson — Mon, 03 Feb 2020 19:51:03 GMT

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?

RE: CE- Sheet Index

mwlong — Mon, 03 Feb 2020 14:32:26 GMT

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.

RE: CE- Sheet Index

Mike Thompson — Mon, 03 Feb 2020 03:17:48 GMT

HI there.

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

RE: CE- Sheet Index

mwlong — Thu, 09 Jan 2020 19:58:37 GMT

Oh, we are well aware of the bugs & are feeling the pain of a beta testing mentality. One thing after the other! I did figure out that editing the .xml file was not the solution & that file is not the root of the issue.

RE: CE- Sheet Index

Bob Rayner — Thu, 09 Jan 2020 19:36:52 GMT

[quote userid="5256" url="~/products/microstation/f/microstation-forum/190917/ce--sheet-index"]WE SHOULD NOT NEED TO MODIFY .XML FILES!!!!![/quote]

No, we shouldn't, but I had to (to keep ribbon minimized). We're working with buggy software, think of yourself as a beta tester.

RE: CE- Sheet Index

mwlong — Thu, 09 Jan 2020 19:26:00 GMT

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.